GCJ, libgcc, collect2 and MinGW
Andrew Haley
aph@redhat.com
Mon Jul 3 10:24:00 GMT 2006
Ranjit Mathew writes:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
> First off, does any one know why we explicitly include libgcc's
> spec in the libgcj.spec? The GCC driver already seems to arrange
> for a "%G %L %G" linking sequence, where %G is the libgcc linking
> spec and %L is the GCJ linking spec. Since libgcj.spec includes
> libgcc's spec, we end up specifying libgcc's libraries *three
> times* to a collect2 invocation. Nothing catastrophic as such,
> but still weird.
I suspect it's to do with the linker's strict left-to-right argument
processing.
> On to the main query: Does anyone know the incantation that
> can be used in libgcj.spec to insert in an option that will
> affect even the libgcc spec that appears *before it* in the
> linking sequence? For example, "gcc/config/i386/mingw32.h"
> defines:
Look at libgcj.spec:
%rename lib liborig
*lib: -lgcj -lm -lpthread -ldl %(libgcc) %(liborig)
Andrew.
More information about the Java
mailing list