ok this is a bit strange (maybe not), i do:<br> <br> $ ./configure --disable-alsa --enable-jack --disable-oss<br> checking for gcc... gcc<br> checking for C compiler default output file name... a.out<br> checking whether the C compiler works... yes<br> checking whether we are cross compiling... no<br> checking for suffix of executables...<br> checking for suffix of object files... o<br> checking whether we are using the GNU C compiler... yes<br> checking whether gcc accepts -g... yes<br> checking for gcc option to accept ANSI C... none needed<br> checking for g++... g++<br> checking whether we are using the GNU C++ compiler... yes<br> checking whether g++ accepts -g... yes<br> checking whether we are using the GNU C++ compiler... (cached) yes<br> checking whether g++ accepts -g... (cached) yes<br> checking how to run the C preprocessor... gcc -E<br> checking for egrep... grep -E<br> checking for ANSI C header files... yes<br> checking for sys/types.h... yes<br> checking for
sys/stat.h... yes<br> checking for stdlib.h... yes<br> checking for string.h... yes<br> checking for memory.h... yes<br> checking for strings.h... yes<br> checking for inttypes.h... yes<br> checking for stdint.h... yes<br> checking for unistd.h... yes<br> checking fcntl.h usability... yes<br> checking fcntl.h presence... yes<br> checking for fcntl.h... yes<br> checking sys/ioctl.h usability... yes<br> checking sys/ioctl.h presence... yes<br> checking for sys/ioctl.h... yes<br> checking sys/time.h usability... yes<br> checking sys/time.h presence... yes<br> checking for sys/time.h... yes<br> checking termio.h usability... yes<br> checking termio.h presence... yes<br> checking for termio.h... yes<br> checking for unistd.h... (cached) yes<br> checking for an ANSI C-conforming const... yes<br> checking for size_t... yes<br> checking whether time.h and sys/time.h may both be included... yes<br> checking whether byte ordering is bigendian... no<br> checking for RAWWAVE_PATH
argument...<br> checking for INCLUDE_PATH argument...<br> checking whether to compile realtime support... yes<br> checking for cos in -lm... yes<br> checking for pthread_create in -lpthread... yes<br> checking for gettimeofday... yes<br> checking for select... yes<br> checking for socket... yes<br> checking whether to compile debug version... no<br> checking build system type... i686-pc-linux-gnu<br> checking host system type... i686-pc-linux-gnu<br> checking for audio API... checking for snd_pcm_open in -lasound... yes<br> using ALSA<br> checking whether gcc needs -traditional... no<br> checking for strstr... yes<br> configure: creating ./config.status<br> config.status: creating src/Makefile<br> config.status: creating projects/demo/Makefile<br> config.status: creating projects/effects/Makefile<br> config.status: creating projects/ragamatic/Makefile<br> config.status: creating projects/examples/Makefile<br> config.status: creating projects/examples/libMakefile<br> <br> <br> After
that i go to src/ and do make, look the macros being passed<br> <br> $ make<br> g++ -O3 -Wall -g -D__GXX__ -I../include -D__LITTLE_ENDIAN__ -D__LINUX_ALSA__ -D__LINUX_ALSASEQ__ -DRAWWAVE_PATH=\"../rawwaves/\" -c Stk.cpp -o Release/Stk.o<br> g++ -O3 -Wall -g -D__GXX__ -I../include -D__LITTLE_ENDIAN__ -D__LINUX_ALSA__ -D__LINUX_ALSASEQ__ -DRAWWAVE_PATH=\"../rawwaves/\" -c Generator.cpp -o Release/Generator.o<br> g++ -O3 -Wall -g -D__GXX__ -I../include -D__LITTLE_ENDIAN__ -D__LINUX_ALSA__ -D__LINUX_ALSASEQ__ -DRAWWAVE_PATH=\"../rawwaves/\" -c Noise.cpp -o Release/Noise.o<br> make: *** [Noise.o] Interrupt<br> <br> <br> It's maybe a problem in the configuration step?<br><br><b><i>"Gary P. Scavone" <gary@ccrma.stanford.edu></i></b> escribió:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> Hi Charles,<br><br>Perhaps you can recompile with only Jack support and see what <br>happens. Any error reports
from STK or RtAudio would be useful.<br><br>Regards,<br><br>--gary<br><br>On 9-Feb-06, at 10:41 PM, Charlls Quarra wrote:<br><br>><br>> Yes, jackd is running before starting the prog, i checked that the <br>> samplerate were teh same just in case. other examples like <br>> sineosc.cpp and foursine.cpp work ok, so the problem seems to be <br>> the jack hook. the jack console doesnt report anything relevant, <br>> besides a couple of xruns<br>><br>> "Gary P. Scavone" <gary @ccrma.stanford.edu=""> escribió: Hi Charlls,<br>><br>> If you compile for all options, the order of priority is: Jack, ALSA,<br>> OSS.<br>><br>> If you indeed have Jack support compiled in, then you need to have<br>> the Jack server running _BEFORE_ starting your application.<br>><br>> Regards,<br>><br>><br>> ¡Llamá a todo el mundo con las mejores tarifas!<br>> Comprá tus tarjetas de llamadas en tres simples pasos<br>> en Yahoo!
Telefonía<br><br></gary></blockquote><br><p>
<hr size=1>
<font color="#9900FF"><b>1GB gratis</b></font>, Antivirus y Antispam<br>
<font color="#9900FF">Correo Yahoo!</font>, el mejor correo web del mundo<br>
<a href="http://login.yahoo.com/config/mail?.intl=ar">Abrí tu cuenta aquí</a>