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


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: multiarch proposal


David Miller <davem@davemloft.net> writes:

> From: Daniel Jacobowitz <drow@false.org>
> Date: Fri, 2 May 2008 13:19:18 -0400
>
>> GCC should be the master arbiter of this sort of path logic, so that
>> ld does not have to care.
>
> I agree completely.

Why?

Ld already cares and has always done so. gcc only adds its own logic
on top of ld for its additional directories.

Ld already cares for [/usr][/local]/lib, [/usr][/local]/lib32,
[/usr][/local]/lib64, /usr[/local]/$TOOL_DIR/lib. In words that is
the system dirs, 32bit dirs, 64bit dirs and cross-compile dirs.

It would be perfectly fine for gcc to only add
-L/usr/lib/gcc/x86_64-linux-gnu/4.2.3,
-L/usr/lib/gcc/x86_64-linux-gnu/4.2.3/32
or
-L/usr/lib/gcc/x86_64-linux-gnu/4.2.3/64
depending on the multilib mode.

Not adding the multiarch dirs to ld the same way seems short
sighted. Adding them to binutils "fixes" both binutils and gcc. Adding
them to gcc only fixes gcc.

MfG
        Goswin


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