On Wed, 19 Apr 2006 16:27:47 +0200 "Nick Copeland" <nickycopeland@xxxxxxxxxxx> wrote: > > Bristol does a rather lightweight check for the presence of Jack - I > did say it was the first release. Version 0.9.4-1 wants the header > files in /usr/local/include/jack, the default location, and if they > are not found there then compilation takes place without jack > support. This will change in a present upload, using jack.pc instead > to find the true location. > > You can 'resolve' this by doing the following: > > # mkdir /usr/local/include/jack > # cd <bristol>/src > # ./build clean > # ./build > > When the directory is there the compilation will continue, and I > assume that the header files will be present in some other more > defualt location (such as /usr/include?). This may also fail if you > have installed the Jack header files in some other location > completely - you can hack the build scripts or send me an email, or > wait for the present 0.9.4-X that will be uploaded soon. > > Regards, > Nick. > Hmm just tried 0.9.4-1.src.041906 compiled as you explained above, but i don't seem to be able to get it to use jack. i did: $ startBristol -b3 -jack & or -audio jack but it starts using alsa. Any hints? :) Regards tom
