gcc-4.2.2 on x86_64 - gcc/32/llibgcc.a - Archive has no index

gcc-4.2.2 on x86_64 - gcc/32/llibgcc.a - Archive has no index

[Poor Yorick]

gcc-4.2.2 on x86_64, with binutils-2.18, build fails.  I think this is the
relevant message from x86_64-unknown-linux-gnu/32/libmudflap/config.log:


    configure:2311: /path/to/src/gcc-4.2.2/gcc-4.2.2_build/./gcc/xgcc -B/path/to/src/gcc-4.2.2/gcc-4.2.2_build/./gcc/ -B/path/to/gcc-4.2.2/x86_64-unknown-linux-gnu/bin/ -B/path/to/gcc-4.2.2/x86_64-unknown-linux-gnu/lib/ -isystem /path/to/gcc-4.2.2/x86_64-unknown-linux-gnu/include -isystem /path/to/gcc-4.2.2/x86_64-unknown-linux-gnu/sys-include  -m32 -O2 -g -O2    conftest.c  >&5
    /path/to/src/gcc-4.2.2/gcc-4.2.2_build/./gcc/32/libgcc.a: could not read symbols: Archive has no index; run ranlib to add one

This message from the binutils list seems relevant:

    http://sourceware.org/ml/binutils/2007-09/msg00150.html

        "You can specify the default target for all the GNU binutils by setting
        the GNUTARGET environment variable.  This is sort of documented in the
        binutils manual."

But I have no idea how to apply this information as a workaround to get gcc-4.2.2 buikld on x86_64.  Any ideas?


-- 
Yorick

Re: gcc-4.2.2 on x86_64 - gcc/32/llibgcc.a - Archive has no index

[Jim Wilson]

Poor Yorick wrote:
>     configure:2311: /path/to/src/gcc-4.2.2/gcc-4.2.2_build/./gcc/xgcc -B/path/to/src/gcc-4.2.2/gcc-4.2.2_build/./gcc/ -B/path/to/gcc-4.2.2/x86_64-unknown-linux-gnu/bin/ -B/path/to/gcc-4.2.2/x86_64-unknown-linux-gnu/lib/ -isystem /path/to/gcc-4.2.2/x86_64-unknown-linux-gnu/include -isystem /path/to/gcc-4.2.2/x86_64-unknown-linux-gnu/sys-include  -m32 -O2 -g -O2    conftest.c  >&5
>     /path/to/src/gcc-4.2.2/gcc-4.2.2_build/./gcc/32/libgcc.a: could not read symbols: Archive has no index; run ranlib to add one
> This message from the binutils list seems relevant:

That doesn't look relevant to me.  A properly built x86_64-linux 
binutils will automatically handle both 32-bit and 64-bit libraries.

Did you check the libgcc.a library to make sure it is OK?

Did you build your own copy of binutils?  Did you check to make sure it 
is OK?

Jim