|
»
« Return to Thread: packager question... how do you like 32bit libs to be built ?
Re: packager question... how do you like 32bit libs to be built ?
by torbenh
::
Rate this Message:
On Thu, May 28, 2009 at 05:47:41PM +0000, Fernando Lopez-Lezcano wrote:
> On Thu, 2009-05-28 at 17:17 +0200, torbenh@... wrote:
> > 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 ?
>
> In x86_64? Yes, at least in Fedora that is where 64 bit libraries land.
strange decision... well... not my beer.
>
> > 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 ?
>
> Hmm, not for me. The "official" jack in Fedora in the 64 bit distro has
> two packages, the 64 bit one and the 32 bit build as well. But that is
> not a 32 bit library built while the 64 bit package is built.
>
> > 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.
>
> I think that is the case. What is the difference between that 32 bit
> library and the one in --mixed? I have not idea...
>
> > 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 think it should not be the default (but I don't really understand what
> it is).
well --mixed changes the datastructures in shared mem in a way that
makes it possible, that a 32bit app can connect to a 64bit server.
it does not make sense to distribute a 32bit libjack for a 64bit system
if it cant connect to jackd which is likely to be a 64bit binary.
So the default is... its not possible and if you distribute 32bit
libjack you are distributing a broken one.
>
> > 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.
>
> Probably not, at least in my case.
what is your case ? you are either building a package via a script, so
you can just add --dont-build-32bitlib or whatever.
or you build a source version from svn or whatever. then i guess youd
like the 32bit lib updated also, because otherwise youd end up with a
libjack on your system which cant connect to jackd.
>
> -- Fernando
>
--
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
> On Thu, 2009-05-28 at 17:17 +0200, torbenh@... wrote:
> > 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 ?
>
> In x86_64? Yes, at least in Fedora that is where 64 bit libraries land.
strange decision... well... not my beer.
>
> > 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 ?
>
> Hmm, not for me. The "official" jack in Fedora in the 64 bit distro has
> two packages, the 64 bit one and the 32 bit build as well. But that is
> not a 32 bit library built while the 64 bit package is built.
>
> > 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.
>
> I think that is the case. What is the difference between that 32 bit
> library and the one in --mixed? I have not idea...
>
> > 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 think it should not be the default (but I don't really understand what
> it is).
well --mixed changes the datastructures in shared mem in a way that
makes it possible, that a 32bit app can connect to a 64bit server.
it does not make sense to distribute a 32bit libjack for a 64bit system
if it cant connect to jackd which is likely to be a 64bit binary.
So the default is... its not possible and if you distribute 32bit
libjack you are distributing a broken one.
>
> > 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.
>
> Probably not, at least in my case.
what is your case ? you are either building a package via a script, so
you can just add --dont-build-32bitlib or whatever.
or you build a source version from svn or whatever. then i guess youd
like the 32bit lib updated also, because otherwise youd end up with a
libjack on your system which cant connect to jackd.
>
> -- Fernando
>
--
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
« Return to Thread: packager question... how do you like 32bit libs to be built ?
| Free embeddable forum powered by Nabble | Forum Help |
