This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC 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: [ping2] Re: [ping] Re: [patch] PR40134, use a linker script on arm-linux to link with -lgcc_s -lgcc


* Matthias Klose wrote on Thu, Nov 12, 2009 at 07:18:47PM CET:
> On 02.11.2009 17:28, Paolo Carlini wrote:
> >Matthias Klose wrote:
> >>I checked that it does (at least on arm-linux-genueabi). IIUC the
> >>schema to do so implemented by Jakub and Alexandre can be extendend to
> >>targets that need to link with libgcc as well. Currently it is used
> >>for powerpc-linux and arm-linux-gnueabi (and linux-sh using it's own
> >>variant). I would have to look up hppa again.
> >Yes, my point is exactly that that kind of scheme (
> >http://gcc.gnu.org/ml/gcc-patches/2009-07/msg00324.html, or equivalent)
> >must be really adopted, fixing only arm-linux isn't enough.
> 
> In http://gcc.gnu.org/ml/gcc-patches/2009-07/msg00733.html I wrote
> that this scheme requires fixing libtool; I never got feedback from
> the libtool maintainers.

What would you suggest as the algorithm to fix it in libtool?
Mind you, I've probably forgotten parts of this, so please bear
with me:

Should libtool always reorder -lgcc_s before -lgcc if it sees
(or is to emit) both?  On all systems?  If not, on which?
Which of the two should it reorder, and where, if the two do
not occur successively?  What if another library dependency
drags in one but not the other, and we already have seen one
or both?

FWIW, I never saw a workable approach fixing libtool only,
nor understood how libtool could be fixed consistently.

Thanks,
Ralf


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