Hi,

(this happens on a embedded system)

I ran into a problem I think...

As adviced I run 

    emerge --depclean -v -p

after a greater update to world.
(by the way: Updateing the world is generally to a bad idea...;)

Beside other things, gcc-4.7.3 was slated for removal. As 
gcc-4.8.3 was already installed and gcc-config shows that it
is active, I started the above command without "-p"....
And it screws up the whole thing badly:
There were many, many applications (the shell for example...)
which were directly linked to
/usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.7.3/libgcc_s.so.1
and/or
/usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.7.3/libstdc++.so.6

After clearing the sdcard and reinstalling the backup I started
to emerge all affected ebuilds by hand...only to find, that they
were again linked against the old libs.

I checked again with gcc-config and found:

beagleboneblack:/root>gcc-config -L
/usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.8.3
beagleboneblack:/root>gcc-config -c
armv7a-hardfloat-linux-gnueabi-4.8.3
beagleboneblack:/root>gcc-config -E
export 
PATH="/usr/armv7a-hardfloat-linux-gnueabi/gcc-bin/4.8.3:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/bin/:/opt/bin:/usr/armv7a-hardfloat-linux-gnueabi/gcc-bin/4.8.3:/usr/games/bin:/root/bin"
export GCC_SPECS=""


What is going on here? Why still the old compiler and its libraries
are used? How can I convince Gentoo to finally switch ti gcc-4.8.3?

What do you think?

Best regards,
Meino





Reply via email to