stuck with broken gcc (Solved)

[djtreble]

Code: Select all

georgeii linux # make menuconfig  
  HOSTCC  scripts/basic/fixdep
/usr/lib/gcc/i486-pc-linux-gnu/4.1.2/../../../../i486-pc-linux-gnu/bin/ld: cannot find -lgcc_s
collect2: ld returned 1 exit status
make[1]: *** [scripts/basic/fixdep] Error 1
make: *** [scripts_basic] Error 2 

eeep

Code: Select all

georgeii linux # gcc-config -l
 [1] i486-pc-linux-gnu-4.1.2
 [2] i686-pc-linux-gnu-4.1.2
 [3] i686-pc-linux-gnu-4.2.4
 [4] i686-pc-linux-gnu-4.3.1 * 

Code: Select all

georgeii linux # gcc -v
Using built-in specs.
Target: i486-pc-linux-gnu 

huh?

Code: Select all

georgeii linux # gcc-config i686-pc-linux-gnu-4.3.1
 * Switching native-compiler to i686-pc-linux-gnu-4.3.1 ...                                           [ ok ]
georgeii linux # env-update && source /etc/profile
>>> Regenerating /etc/ld.so.cache...
georgeii linux # gcc -v
Using built-in specs.
Target: i486-pc-linux-gnu

/me bangs head against wall.

I have the latest version of gcc-config 1.4.1

Any ideas?

Thanks

Dan

I'm sure this is a known and fixed problem, I find the forum search infuriating though.

Try searching for "gcc-version" "gcc -v" and it screws it all up

[djtreble]

Things just get worse! How many versions of gcc can one error mention.

Code: Select all

lzma: /usr/lib/gcc/i486-pc-linux-gnu/4.1.2/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/gcc/i686-pc-linux-gnu/4.3.3/libstdc++.so.6)

Answer : 3

[djtreble]

So I did something nasty

Code: Select all

mv /usr/bin/gcc /usr/bin/gccold
ln -s /usr/bin/gcc-4.3.3 /usr/bin/gcc

I decided to re emerge gcc-4.3.3, I watched it compile 4.3.3

However it's only gone and replaced my /usr/bin/gcc again with the old one.

Code: Select all

# gcc -v
Using built-in specs.
Target: i486-pc-linux-gnu
Configured with: /var/tmp/portage/sys-devel/gcc-4.1.2/work/gcc-4.1.2/configure

I'm losing my mind

[emerald]

You're probably hitting a problem i discovered some time ago when i set up a system starting from a stage1.
There, when unmerging the pre-stage1 gcc during bootstrap it left some files, dirs and symlinks in /usr/gcc or /usr/lib (don't remember exactly anymore) and /etc/env.d(/gcc)?, which cause the system to access those and fail pityfully to build anything.
I'd recommend to check all mentionend directories for wrong/left over files from a i486 gcc-4.1.

[djtreble]

Thanks

Code: Select all

./etc/eselect/compiler/i486-pc-linux-gnu-4.1.2.conf
./etc/env.d/gcc/i486-pc-linux-gnu-4.1.2
./etc/env.d/gcc/config-i486-pc-linux-gnu
./etc/env.d/binutils/config-i486-pc-linux-gnu
./etc/env.d/binutils/i486-pc-linux-gnu-2.18
./etc/env.d/05gcc-i486-pc-linux-gnu
./usr/libexec/gcc/i486-pc-linux-gnu
./usr/i486-pc-linux-gnu
./usr/i486-pc-linux-gnu/gcc-bin/4.1.2/i486-pc-linux-gnu-gcc
./usr/i486-pc-linux-gnu/gcc-bin/4.1.2/i486-pc-linux-gnu-gcc-4.1.2
./usr/lib/perl5/5.8.8/i486-linux
./usr/lib/gcc/i486-pc-linux-gnu
./usr/lib/binutils/i486-pc-linux-gnu
./usr/share/gcc-data/i486-pc-linux-gnu
./usr/share/binutils-data/i486-pc-linux-gnu
./usr/bin/i486-pc-linux-gnu-strip
./usr/bin/i486-pc-linux-gnu-strings
./usr/bin/i486-pc-linux-gnu-size
./usr/bin/i486-pc-linux-gnu-readelf
./usr/bin/i486-pc-linux-gnu-ranlib
./usr/bin/i486-pc-linux-gnu-objdump
./usr/bin/i486-pc-linux-gnu-objcopy
./usr/bin/i486-pc-linux-gnu-nm
./usr/bin/i486-pc-linux-gnu-ld
./usr/bin/i486-pc-linux-gnu-gprof
./usr/bin/i486-pc-linux-gnu-c++filt
./usr/bin/i486-pc-linux-gnu-as
./usr/bin/i486-pc-linux-gnu-ar
./usr/bin/i486-pc-linux-gnu-addr2line
./usr/bin/i486-pc-linux-gnu-gcc
./usr/i686-pc-linux-gnu/i486-pc-linux-gnu
./var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/libstdc++-v3/config/abi/i486-linux-gnu
./var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/libstdc++-v3/config/cpu/i486
./var/tmp/portage/sys-libs/libstdc++-v3-3.3.6/work/gcc-3.3.6/libstdc++-v3/config/abi/i486-linux-gnu
./var/tmp/portage/sys-libs/libstdc++-v3-3.3.6/work/gcc-3.3.6/libstdc++-v3/config/cpu/i486
./var/tmp/portage/dev-libs/gmp-4.2.4/work/gmp-4.2.4/mpn/x86/i486

zap them?

[emerald]

...probably...
Maybe check with qfile (portage-utils) which package they belong to, but very likely you can delete them all
After cleaning the env.d dir it should be alright already, at least no more broken compiler and such.
Check the gcc/binutils directories, it should be very obvious if they are still being used or just leftover cruft. In case you are not completely sure rename them or move them to another location first but they all are probably not used anywhere.

[djtreble]

Solved. Thank you.

You sir, emerald, have saved me a day.