Re: [gentoo-dev] The dreaded debug use flag/eclass
On Wednesday 03 August 2005 15:11, Danny van Dyk wrote: Mike Frysinger schrieb: | On Wednesday 03 August 2005 07:16 am, Martin Schlemmer wrote: |On Tue, 2005-08-02 at 09:22 -0400, Mike Frysinger wrote: |On Monday 01 August 2005 10:43 pm, Danny van Dyk wrote: | |Last time I checked, only --without-pic or --disable-static disable |compiling twice. | | my tests show that with libtool 1.5.18 --without-pic doesnt change | anything ... obviously --disable-static changes things same as | --disable-shared would :P | | maybe i just did it wrong ... i used imlib2-1.2.0 as a reference | -mike According to libtool's source, it only compiles things twice if it shall build 'old-libs' ($build_old_libs=yes) _and_ shared libraries. If it builds 'libtool-libs' ($build_libtool_libs=yes) it uses the same object files for both the static and the shared library. But I might be comletely wrong... libtool's internals are sometimes so confusing :-/ It shouldn't, and I believe it doesn't. Static libraries should be built without -pic, and shared with. Of course static libraries with pic do work, but it is a suboptimal solution. (Unless you want to include said static library into a shared library). Just see a static library as nothing more or less than a system archive of object files that applications can include. Paul -- Paul de Vrieze Gentoo Developer Mail: [EMAIL PROTECTED] Homepage: http://www.devrieze.net pgpr0ndTu3BUj.pgp Description: PGP signature
Re: [gentoo-dev] The dreaded debug use flag/eclass
On Tue, 2005-08-02 at 09:22 -0400, Mike Frysinger wrote: On Monday 01 August 2005 10:43 pm, Danny van Dyk wrote: Mike Frysinger schrieb: |your USE=pic example is wrong, it does not change CFLAGS (and if your |package does, it is broken) chillispot at least is not wrong. If USE=pic is set, it compiles _only with_ -fPIC, ommiting to compile files twice and effectivly telling libtool not to produce a normal static library. just to review ... `use_with pic` should never be used because if you dont have 'pic' in your USE flags, the ebuild will run `./configure --without-pic` ... that means libtool will try to produce shared and static libraries with object files which were built without PIC ... on many arches (like amd64), the linker will abort btw, where do you get this information ? my tests show that libtool still compiles all files twice even though --with-pic was used ... Last time I checked, only --without-pic or --disable-static disable compiling twice. -- Martin Schlemmer signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] The dreaded debug use flag/eclass
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike Frysinger schrieb: | On Monday 01 August 2005 10:43 pm, Danny van Dyk wrote: | |chillispot at least is not wrong. If USE=pic is set, it compiles _only |with_ -fPIC, ommiting to compile files twice and effectivly telling |libtool not to produce a normal static library. | | | not really | | chillispot doesnt build/install any libraries | -mike Heh, in this case the --with-pic option for configure is useless and has no effect :-/ Danny - -- Danny van Dyk [EMAIL PROTECTED] Gentoo/AMD64 Project, Gentoo Scientific Project -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC71SuaVNL8NrtU6IRAoLuAJ9Iq7OjfP20V1cnmYyHhlgSJnUxuQCdE61f UdWn3jR83wmZftVQIBrmSCQ= =25Q6 -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] The dreaded debug use flag/eclass
On Monday 01 August 2005 10:43 pm, Danny van Dyk wrote: Mike Frysinger schrieb: |your USE=pic example is wrong, it does not change CFLAGS (and if your |package does, it is broken) chillispot at least is not wrong. If USE=pic is set, it compiles _only with_ -fPIC, ommiting to compile files twice and effectivly telling libtool not to produce a normal static library. just to review ... `use_with pic` should never be used because if you dont have 'pic' in your USE flags, the ebuild will run `./configure --without-pic` ... that means libtool will try to produce shared and static libraries with object files which were built without PIC ... on many arches (like amd64), the linker will abort btw, where do you get this information ? my tests show that libtool still compiles all files twice even though --with-pic was used ... -mike -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] The dreaded debug use flag/eclass
On Monday 01 August 2005 09:22 pm, Alec Warner wrote: Many people do not like the fact that a USE flag changes CFLAGS. Although there are other USE flags that do this too ( pic comes to mind in a couple ebuilds, checkpassword fex ) they are a minority compared to debug. your USE=pic example is wrong, it does not change CFLAGS (and if your package does, it is broken) -mike -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] The dreaded debug use flag/eclass
On Monday 01 August 2005 10:43 pm, Danny van Dyk wrote: chillispot at least is not wrong. If USE=pic is set, it compiles _only with_ -fPIC, ommiting to compile files twice and effectivly telling libtool not to produce a normal static library. not really chillispot doesnt build/install any libraries -mike -- gentoo-dev@gentoo.org mailing list
