I have gcc 3.3.5 emerged. Nevertheless, faad2-2.0-r4 try to link with 3.4.1/libstdc++.la (and, of course, emerging fails): ... mkdir .libs libtool: link: cannot find the library `/usr/lib/gcc/i686-pc-linux-gnu/3.4.1/libstdc++.la' ... My system is synced with ~x86 except for gcc 3.4.x which is masked. Plenty of other apps work and (re)emerge without any problems.
You can't mix gcc 3.3.x and gcc 3.4.x. Choose the compiler you want to use with gcc-config and run `revdep-rebuild -X -soname <foo>`, where <foo> is libstdc++.so.6, if you want to stay with gcc 3.3 and libstdc++.so.5 otherwise.
Carsten, I'm not sure the metod you have suggested will resolve the problem: revdep-rebuild has not found anything about libstdc++.so (only few packages depending on FLAC because of recent FLAC updating were found). And, well, I have not gcc 3.4.x installed at all: # gcc-config -l [1] i686-pc-linux-gnu-3.3.5 * [2] i686-pc-linux-gnu-3.3.5-hardened [3] i686-pc-linux-gnu-3.3.5-hardenednopie [4] i686-pc-linux-gnu-3.3.5-hardenednossp
The question is, if you used 3.4.1 once.
Carsten, You are right, there was short period with gcc 3.4.x. After that I spent many time to eliminate all gcc 3.4.x traces (using revdep-rebuild too). Few last months I have not noticed any problems concerning gcc 3.4.x (few hundreds of packages emerging/updating). Is there way to be sure some gcc 3.4.x traces are still in my system? If it is, I'll try to remove them and to emerge faad2.
As I said: `revdep-rebuild -X -soname libstdc++.so.6`
Carsten, I have (revedep-)rebuilt everything related to FLAC update, and now revdep-rebuild -X -soname libstdc++.so.6 founds nothing to rebuild.
Then you'll most likely have some stale .la files lying around. Marinus: Can this relate to the latest patch?
*** This bug has been marked as a duplicate of 78858 ***
