Compile error: libstdc++

_savage · Guru Joined: 06 Jun 2004 Posts: 308 Location: Redmond, WA

I came across this problem for a little while now, and kept --skipfirst --resume'ing it, assuming it's an ebuild bug which will be fixed soon. But the number of packages failing to build gets longer ;-)

Here's the last build error

keyson · l33t Joined: 10 Jun 2003 Posts: 830 Location: Sweden

Hi.

This is documented on many places in the forum.

Try to run:

jkt · Posted: Fri Apr 15, 2005 3:57 pm Post subject:

Please search the forums. And in case you're too lazy, check out FAQ :roll:

_________________
cd /local/pub && more beer > /dev/mouth

Česká dokumentace

natestone · n00b Joined: 19 Nov 2003 Posts: 4

I have encountered this problem as well and the above post is not the solution.

The problem is that the "libstdc++" files have been compiled using the path "//usr/lib..." rather than "/usr/lib" -- Notice the double slash ("//"). During subsequent builds of other programs, this double slash problem breaks EGREP and SED statements in the build process resulting in the "libstdc++ not found" problem even though it is there.

The fix_libtool_files.sh script has no effect since all it does is check other libs for proper version linking. The problem is with libstdc++ itself.

I've run the fix_libtool_files.sh script anyway and it has no effect. I've also re-emerged gcc (and run the fix_lib.. script) and can not solve the problem.

gcc-3.3.5 or gcc-3.3.5-20050130 both exhibit the problem on my system. About 60% of all builds fail due to this problem.

Any help would be much appreciated.

Thanks,
Nate
_________________
www.keenspot.com = good

jkt · Posted: Thu Apr 21, 2005 1:06 pm Post subject:

_savage · Guru Joined: 06 Jun 2004 Posts: 308 Location: Redmond, WA

jkt · Posted: Thu Apr 21, 2005 3:02 pm Post subject:

bruda · Posted: Thu Apr 21, 2005 3:35 pm Post subject:

natestone · n00b Joined: 19 Nov 2003 Posts: 4

Thanks for all of your help folks. I really appreciate it.

And, you are (of course) correct.

The problem was that I was not appending the "--oldarch" option on fix_libtool_files.sh when running it. Since the tool would output a few changed files when I ran it, I assumed that everything else was fine. In fact, everything that I had installed from the Packages CD was not linked to my current ARCH and the libtool ignored these as potential linking problems.

When I ran with the oldarch flag set to "i386-pc-linux-gnu", about 500 libraries were changed and things are in proper order now.

Perhaps, the fix_libtool_files.sh script could detect the ARCH automatically and check for improper ARCH matches as it scans for the version fixes. I don't know who to suggest that to, but it seems that most users would want everything linked to the current ARCH at all times and that the data is always present on the machine to tell what ARCH you are currently running.

Anyway, thanks again.

--Nate
_________________
www.keenspot.com = good