[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
using ld for linking non-C code (was: [REBASED PATCH 0/9] Paolo's sysroo
From: |
Ralf Wildenhues |
Subject: |
using ld for linking non-C code (was: [REBASED PATCH 0/9] Paolo's sysroot patches, rebased plus some fixes) |
Date: |
Sun, 1 Aug 2010 12:46:22 +0200 |
User-agent: |
Mutt/1.5.20 (2010-04-22) |
* Charles Wilson wrote on Mon, Jul 26, 2010 at 01:57:57PM CEST:
> As an aside, WHY is it that libtool tries to figure out what the language
> driver
> does, and use ld directly, rather than just trust the language driver and use
> it
> to link instead? It seems that the current libtool behavior causes a lot of
> problems because it is quite fragile...
Because for a long time, the drivers were broken? (I don't know.)
Because that allows it to set run paths to the compiler libs?
(I don't know either.)
It precedes my time anyway. We should clean it up and disable it for
the compilers and systems where we know that it works. That is a
separate issue, and hopefully we can keep it separate, but IIUC it
influences this patch series and how much work it is to get right.
Not sure which strategy would be easiest for you.
Cheers,
Ralf
- using ld for linking non-C code (was: [REBASED PATCH 0/9] Paolo's sysroot patches, rebased plus some fixes),
Ralf Wildenhues <=