This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Some inconsistency in collect2, with respect to gcc and libtool
- To: Marc Espie <Marc dot Espie at liafa dot jussieu dot fr>
- Subject: Re: [PATCH] Some inconsistency in collect2, with respect to gcc and libtool
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Tue, 11 Jul 2000 22:16:36 -0600
- cc: gcc at gcc dot gnu dot org, libtool at gnu dot org, gcc-patches at gcc dot gnu dot org, David Mazieres <dm at reeducation-labor dot lcs dot mit dot edu>, Todd dot Miller at courtesan dot com, niklas at appli dot se
- Reply-To: law at cygnus dot com
In message <20000710171947.A15506@liafa1.liafa.jussieu.fr>you write:
> Collect2 has some code to parse arguments which is less than perfect,
> especially when one takes libtool into account.
>
> Specifically, gcc specs documentation explicitly says that any file that do
> es
> not have default rules will be transparently passed to the linker.
>
> On the other hand, collect2's parser does only recognize .o files as proper
> object files.
>
> What this means is that libtool CAN'T support .lo on any platform that reli
> es
> on collect2 to do its job.
>
> This is especially important for C++, where g++ -shared might be the only
> sane way to ensure constructors are going to be called.
>
> So, I'm wondering about how to fix that. A simple fix would be tell collect
> 2
> that .lo are also object files. Here it is:
>
> Mon Jul 10 17:10:09 MET DST 2000 Marc Espie <espie@openbsd.org>
> * collect2.c (main): Recognize .lo as object files.
Installed based on Jason's approval.
jeff