Re: [PATCH] Look for libraries in "lib64" as well as in "lib"

[Ralf Corsepius <rc040203 at freenet dot de>]

 On 09/29/2010 04:51 PM, Mike Frysinger wrote:
> On Wednesday, September 29, 2010 10:37:32 Ralf Corsepius wrote:
> > On 09/29/2010 04:32 PM, Anthony Foiani wrote:
> > > # HG changeset patch
> > > # User Anthony Foiani<anthony.foiani@gmail.com>
> > > # Date 1285770476 21600
> > > # Node ID 5676bb6d9d7a61a062d0b8bf86c9ddccfcae4f7c
> > > # Parent  ff2181adbd28c91a21fa5f230bf92aaa7824dc73
> > > Look for libraries in "lib64" as well as in "lib".
> > >
> > > On Fedora x86_64 systems, many libraries are in "lib64" directories,
> > > not plain old "lib".
> > This patch doesn't make sense: lib64 and lib are not supposed to be
> > mixed, but to be mutually exclusive.
> yes, but the script has a hard time figuring out which the build system should
> be using
Right, this is a design limitation.

Instead of poking around into run-time libraries, it should try to 
examine the system by using the mechanisms gcc provides, eg.:
gcc $CFLAGS -print-multi-os-directory
or to apply compile/linktests (this is what autoconf does)
or to let the user manually specify settings (This is what fedora does 
when building fedora packages).

> a better idea though would be to simply sync up with the code in the linux
> kernel as it already works with multilib systems -- it has dropped the manual
> library search patch
Sorry, I am not familiar with this approach - I am a GCC and a Fedora 
guy, not a kernel guy ;)

Ralf



--
For unsubscribe information see http://sourceware.org/lists.html#faq