On 11-01-2008 21:52:08 -0500, Mike Frysinger wrote: > On Tuesday 08 January 2008, Fabian Groffen wrote: > > - sort out the 64-bits targets with their multilib-hell forced upon us > > dont know exactly what you're referring to, but multilib is completely > optional.
http://article.gmane.org/gmane.linux.gentoo.alt/3329 In short: gcc inserts 64-bits library paths which causes the linker first to look inside the host dirs, then in my prefix lib dirs, which creates interesting problems, since the runtime linker gets our runpath directions to look in the prefix lib dirs first. Anyway, it makes linking/runtime fail in cases where the host provided libs are incompatible with the prefix provided ones. Added to that that when I implemented the ldwrapper on amd64 (fedora) linux I didn't fully understand the full multilib picture, some decisions I made there now just feel plain wrong, especially given that each distro seems to implement the multilib thing different (Gentoo: /lib = native bits size, Fedora: /lib = 32-bits, Debian ...). I didn't get it fully right in my post above though, because every distro/os has a kernel configured in such a way that for a 64-bits object, the search path points to the 64-bits host-specific lib paths. So it seems that only binutils doesn't want to know about 64-bits host-specific lib paths, and gcc takes actions to compensate that. Thanks. -- Fabian Groffen Gentoo on a different level -- gentoo-dev@lists.gentoo.org mailing list
