./configure
In fact, running just ./configure will also print out the detected audio backends and warn you if it doesn't find some things. This has been true since the auto tools update was merged around 0.47.
Message: 3Date: Fri, 15 Feb 2019 10:30:07 +0100From: IOhannes m zmölnig <zmoelnig@iem.at>To: pd-list@lists.iem.atSubject: Re: [PD] Issue compiling pure data on FedoraMessage-ID: <61e14c57-6d9f-0bf9-dc1a-4f355f235e54@iem.at>Content-Type: text/plain; charset="utf-8"On 2/15/19 7:16 AM, William Binta wrote:Hi list,
I'm new to Linux and particullary to the Fedora distribution. But as some
people, I failed at installing the last build (0.49) on Fedora 29.
I precisely followed the steps on the INSTALL.txt, installed every thing
necessary mentioned for a successful compilation but yet, my pure-data
installation doesn't detects any audio devices. I get the "priority 92
scheduling failed; running at normal priority" on the pd console and
"priority 94 scheduling failed" error message on the terminal.
Even though I enabled jack on the "configure" step and put the -jack flag,
I read on the terminal that pure-data was not build with JACK.
you must install the headers for ALSA and JACK prior to running./configure, if you want to use them.something like:# yum install jack-audio-connection-kit-devel alsa-develalso:My installation configuration was= ./configure --enable-jack
--enable-fftw --enable-universal=x86_64 --disable-oss--without-local-portaudio"--enable-universal" sounds very much like a OSX flag (i just checkedthe INSTALL.txt, and it can indeed be read to suggest this flag)why did you add the "--without-local-portaudio" flag?fgdsarIOhannes