On Thu, May 28, 2009 at 02:54:07PM +0000, Fernando Lopez-Lezcano wrote:
> On Thu, 2009-05-28 at 07:22 +0200,
torbenh@... wrote:
> > hi...
> >
> > for me its much more convenient, when the 32bit libjack is built and
> > installed along with a normal 64bit build.
> >
> > i added this to the build scripts of jacknone.
> >
> > are there any concerns from packager side ?
> > iE do you want a configure switch to turn this behaviour off ?
> >
> > please remind me of the different paths for 32bit libs on the different
> > systems. so far the libdir32 is generated by appending 32 to the
> > libdir64.
>
> 32 bits: /usr/lib
> 64 bits: /usr/lib64
is that really the case ? you need to build everything with
LIBDIR=/usr/lib64 ?
i added a libdir32 switch now. should work for everybody.
fernando, i need an answer to the first question though.
does it make sense to you that when jack is built with --mixed it will
also build a 32bit lib ?
this 32bit lib is probably not the same as the normal 32bit lib.
i am not sure how we should behave. stephane made --mixed a configure
option, and even off by default.
it only makes sense on a 64bit system. but it looks like packagers just
use i386 builds as 32bit packages.
so
a) jack x86_64 package conatains a 32bit lib.
b) --mixed will be default, and you will be able to use the normal
i386 library
i just want that people who build from source have a sort of easy
experiance, and the default on 64bit should be that the 32bit lib is
installed along.
--
torben Hohn
http://galan.sourceforge.net -- The graphical Audio language
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
