| 1 |
Alan Grimes wrote: |
| 2 |
> Holger Hoffstätte wrote: |
| 3 |
>> ..indicates a mismatch in C++11 ABI which changed in gcc5. What happens is that one the |
| 4 |
>> dependencies of openimageio was built against the old C++11 std::string ABI (hence the |
| 5 |
>> link errors), and needs to be rebuilt. It looks to be "Imf" aka libIlmImf, |
| 6 |
>> whatever that is. Try to rebuild it with --oneshot and it should work. |
| 7 |
>> If a similar error pops up for a different dependency, repeat. :) |
| 8 |
>> |
| 9 |
>> -h |
| 10 |
> Yeah, I emptytree world my system after each Y in X.Y.Z compiler version |
| 11 |
> bump. Since I sad it, everyone will tell you it's bad advice but really |
| 12 |
> not. The binary distros will compile everything with the same compiler |
| 13 |
> so crap doesn't happen. Now it's not super important but then you have |
| 14 |
> no idea how many other abi link errors are hiding out there. |
| 15 |
> |
| 16 |
> |
| 17 |
|
| 18 |
I do the same here. When I switch to a new version of gcc, I do a |
| 19 |
emerge -e world. If I've read that it really changes some things, like |
| 20 |
this one appears to do, I do it twice. The second time may be overkill |
| 21 |
but I'd rather have overkill than some weird problem that is difficult |
| 22 |
to figure out the solution. I don't think anyone would say doing that |
| 23 |
is bad. A ounce of prevention is always better than a pound of cure. ;-) |
| 24 |
|
| 25 |
There's another upgrade that I do that after too. I can't recall the |
| 26 |
name right now but maybe it is glibc or something???? |
| 27 |
|
| 28 |
Dale |
| 29 |
|
| 30 |
:-) :-) |
Archives