gcc-2.95 failed to build

Chris Rankin chris@Linux.bim.gantep.edu.tr
Tue Aug 31 22:45:00 GMT 1999


> Did you update via diffs or are you using the tarball?  You do know that
> when you update via diffs you may need other tools such as bison, gperf,
> autoconf, automake, etc.

I used the bz2-compressed diff between egcs-1.1.2 and gcc-2.95; I do
have bison, autoconf and automake and I checked that I had gperf
before I began. However, my c-gperf.h file was suspiciously empty so I
checked my gperf binary again:

$ ldd /usr/bin/gperf
        libg++.so.2.8 => /usr/lib/libg++.so.2.8 (0x4000b000)
        libstdc++.so.2.8 => /libc5/libstdc++.so.2.8 (0x40053000)
        libm.so.5 => /lib/libm.so.5 (0x40097000)
        libc.so.5 => /lib/libc.so.5 (0x4009f000)
        libm.so.6 => /lib/libm.so.6 (0x4015f000)
        libc.so.6 => /lib/libc.so.6 (0x4017c000)
        ld-linux.so.2 => /lib/ld-linux.so.2 (0x4026e000)
/usr/bin/gperf: can't resolve symbol '__vt_3ios'
/usr/bin/gperf: can't resolve symbol '__vt_10ostrstream.3ios'
/usr/bin/gperf: can't resolve symbol '__vt_7ostream.3ios'

A casualtly of war, I think :-). Time to compile a later version ...

Cheers,
Chris.



More information about the Gcc-bugs mailing list