Re: [PATCH] Some inconsistency in collect2, with respect to gcc and libtool

[Marc Espie <espie at quatramaran dot ens dot fr>]

In article <or1z12arib.fsf@guarana.lsd.ic.unicamp.br> you write:
>On Jul 10, 2000, Marc Espie <Marc.Espie@liafa.jussieu.fr> wrote:

>> What this means is that libtool CAN'T support .lo on any platform
>> that relies on collect2 to do its job.

>The libtool multi-language branch, which is the only one that claims
>to support languages other than C, uses only .o files to name object
>files.  PIC object files are now stored in the .libs directory, and
>the .lo file now is a script that names the PIC and the non-PIC object
>files.

Any timeframe as to when this will be ready ?

The reason I'm asking is as follows:
ELF systems don't get through collect2, hence they don't even see the
problem.

So, this means that, right now, we are seeing C++ systems that use
libtool (1.3 ?), and that work only on selected systems... the selected systems
being now ubiquitous enough that there is little pressure to make the rest
of the world work...