The default for the multilib useflag in libstdc++-v3 changed, causing it to be rebuild. This resulted in: !!! existing preserved libs: >>> package: sys-libs/libstdc++-v3-3.3.6-r1 * - /usr/lib32/libstdc++.so.5 * - /usr/lib32/libstdc++.so.5.0.7 * used by /opt/doom3-demo/doom.x86 (games-fps/doom3-demo-1.1.1286) * used by /opt/doom3-demo/gamex86.so (games-fps/doom3-demo-1.1.1286) * used by /opt/quake4-demo/q4ded.x86 (games-fps/quake4-demo-1.0) * used by /opt/quake4-demo/quake4.x86 (games-fps/quake4-demo-1.0) It seems that the DEPEND needs to take the useflag into account. Hmmm, there is currently no dependency on libstdc++-v3 in these ebuilds, they install their own private libstdc++.so.5: thoregon ~ # locate libstdc++.so.5 /opt/doom3-demo/libstdc++.so.5 /opt/quake4-demo/libstdc++.so.5 /usr/lib32/libstdc++.so.5 /usr/lib32/libstdc++.so.5.0.7 /usr/lib64/libstdc++.so.5 /usr/lib64/libstdc++.so.5.0.7 /usr/lib64/debug/usr/lib64/libstdc++.so.5.0.7.debug So is this a bug in portage for misidentifying the need for /usr/lib32/libstdc++.so.5 or should the private libs be replaced by sys-libs/libstdc++-v3[multilib]?
Adding Ian Stakenvicius to CC: I think your doom3-demo-1.1.1286-r1.ebuild just fixed half of this bug, so I thought you should know about it.
Thanks!! I'll mark it RESO/FIXED after I fix the other half. :)
And thanks for your work! I just tested the doom3-demo and it seems to work. At least the intro works and I can start a game. (Its quite a long time I last tried it. That last time would just freeze or crash during the intro. Probably something in mesa got fixed in the last years... ;-) )
Finished quake4-demo today, marking bug fixed.
