| 1 |
On 1/19/06, Jeff <jmg_071769@×××××××.net> wrote: |
| 2 |
> .libs/dynamicrequest.o: In function |
| 3 |
> `Arts::DynamicRequest::~DynamicRequest()': |
| 4 |
> dynamicrequest.cc:(.text+0x1a5): undefined reference to |
| 5 |
> `std::basic_string<char, std::char_traits<char>, std::allocator<char> |
| 6 |
> >::_Rep::_S_empty_rep_storage' |
| 7 |
|
| 8 |
Definitely looks like a gcc 3.3->3.4 upgrade problem... |
| 9 |
|
| 10 |
> |
| 11 |
> Keep in mind, this is happening after I've *carefully* followed the |
| 12 |
> upgrade to gcc-3.4 instructions, and I've done the same exact build on 4 |
| 13 |
> other boxes with no problems. |
| 14 |
|
| 15 |
Some people here have reported trouble, even though they followed the |
| 16 |
instructions. Not sure why. |
| 17 |
|
| 18 |
I suggest: |
| 19 |
|
| 20 |
# gcc-config -l |
| 21 |
# gcc-config <X> (where X is the version of gcc that you want to use, |
| 22 |
if not already set) |
| 23 |
# revdep-rebuild --library=libstdc++.so.5 |
| 24 |
# emerge --ask --pretend --prune sys-devel/gcc |
| 25 |
(the above should want to remove gcc versions prior to <X> above) |
| 26 |
# emerge -e world (this is really optional...do it when you have time) |
| 27 |
|
| 28 |
The revdep-rebuild method seems to have been more reliable for most |
| 29 |
people. Indeed, on my AMD64 box, I tried the emerge -e system route, |
| 30 |
and that ended up switching me back to gcc 3.3 for some reason. |
| 31 |
|
| 32 |
-Richard |
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-user@g.o mailing list |
Archives