2 Dec 2008 08:17
Re: comments on compiling JACK (especially for packagers)
Fernando Lopez-Lezcano <nando <at> ccrma.Stanford.EDU>
2008-12-02 07:17:17 GMT
2008-12-02 07:17:17 GMT
On Tue, 2008-12-02 at 07:44 +0100, Paul Davis wrote: > On Mon, 2008-12-01 at 15:47 -0800, Fernando Lopez-Lezcano wrote: > > On Fri, 2008-11-28 at 15:43 +0100, Paul Davis wrote: > > > I have seen several different packages of JACK and/or their build > > > scripts that are either incorrect, or less than optimal. Users do this > > > too. I think we need to review the options: > > > > > > DETAILS > > > > > > Configure options first, then comments after the option(s). > > > > > > Packages (and users) should probably never ever use these. > > > > > > --enable-dynsimd enable dynamic SIMD selection (default=no) > > > > > > This is a very complex option, and is best left off unless you really > > > know what you are doing. In particular, do not use this with > > > --enable-optimize. > > > > Hmmm, I was using it... so what is the interaction with enable-optimize, > > which I should use (together with optimization-by-compiler)? > > I've fixed all that up now. It now works with --enable-optimize. In > addition, --enable-optimization-by-compiler will not add any > processor-specific compile flags, which it was still doing before. > > fernando, i'm about to release 0.116.0, which properly supports 32/64 > mixed server/client setups, compiles on OS X, has fixes/improvements for > netjack, and has configure improvements. you might want to hold on off > on packaging 0.115.6.(Continue reading)
RSS Feed