This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


On 09/29/2010 04:40 PM, Anthony Foiani wrote:
On Wed, Sep 29, 2010 at 8:37 AM, Ralf Corsepius<rc040203@freenet.de> wrote:

On 09/29/2010 04:32 PM, Anthony Foiani wrote:

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.

Ralf

Sensible or not, I needed this to get my compilation to complete.
More verbose: Your approach is broken.
(I know that some people have criticized the way that Fedora lays out
libraries on x86_64, and I suspect that this is more fallout from before.)
Well, there are many people out, who don't understand how multi-lib'ed toolchains and multi-arch'ed systems (like Fedora) work.
Actually, given Yann's comments on my first submission, it seems that the
Fedora gcc will look in lib64 even when not asked
On Fedora-x86_64
gcc -m64 will look into /usr/lib64
gcc -m32 will look into /usr/lib

Both these library systems must not be mixed during linkage.

  -- but since CT-NG is
looking for library names directly, it needs to look in lib64 as well.
Well, yes, this approach is based on broken assumptions (flawed design).

Ralf


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]