| 1 |
felix@×××××××.com posted 20061027175022.GA16955@×××××××.com, excerpted |
| 2 |
below, on Fri, 27 Oct 2006 10:50:22 -0700: |
| 3 |
|
| 4 |
> Checking DLL |
| 5 |
> ../unxlngx6.pro/lib/check_libucbhelper3gcc3.so ...: ERROR: |
| 6 |
> /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.6/libstdc++.so.6: version |
| 7 |
> `CXXABI_1.3.1' not found (required by |
| 8 |
> ../unxlngx6.pro/lib/check_libucbhelper3gcc3.so) |
| 9 |
|
| 10 |
Richard Fish is on the right track here... that error points to a typical |
| 11 |
mixup between gcc 3.x and 4.x. |
| 12 |
|
| 13 |
However, perhaps the solution is a bit simpler... Have you tried |
| 14 |
running fix_libtool_files.sh with the old gcc version (3.4.6 in this case, |
| 15 |
from the above error)? If not, do so. That's the first thing I try any |
| 16 |
time I get an error pointing to an old gcc version libstdc++, and it |
| 17 |
usually fixes the problem. If not, sometimes it's possible to figure out |
| 18 |
which file the problem is in manually -- do a search in /usr/lib64 (and |
| 19 |
other libdirs, but start with that one) for all *.la files containing 3.4.6 |
| 20 |
and ensure they have the path to your current gcc (4.1.1) as well as the |
| 21 |
old 3.4.6 version. It hasn't happened here in awhile so maybe they fixed |
| 22 |
the problem, but it used to be that fix_libtool_files.sh would |
| 23 |
occasionally miss something. |
| 24 |
|
| 25 |
-- |
| 26 |
Duncan - List replies preferred. No HTML msgs. |
| 27 |
"Every nonfree program has a lord, a master -- |
| 28 |
and if you use the program, he is your master." Richard Stallman |
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-amd64@g.o mailing list |
Archives