I compiled my entire 1.4_rc2 system with USE="static" and everything worked fine except for a few select packages, the packages that failed for me (and im sure there are more) were qt, mozilla, fam-oss, librsvg, and aspell. All of these failed with the same error message about unresolved symbols in std::time_put_w@GLIBCPP_3.2. After some searching and a discussion with rac on irc i found that i had no libstdc++.so.5 anywhere and no libstdc++.so.* in /usr/lib/gcc-lib/ only /usr/lib/gcc-lib/libstdc++.a and libstdc++.la and /usr/lib/libstdc++.so.2.* Remerging gcc with USE="-static" generated the proper libraries and fixed the other ebuilds that were failing. Reproducible: Always Steps to Reproduce: 1. USE="static" emerge gcc 2. emerge fam-oss or other packages that depend on libstdc++.so.5 there may be other considerations such as emerging the broken packages themselves with USE="static" or the fact that my entire system was built with static, however emerging gcc without static and keeping static as a use flag everywhere else worked fine. Actual Results: ld errors about unresolved symbols and std::time_put_w@GLIBCPP_3.2 Expected Results: successful build
Outstanding issue ... you cannot build gcc with g++ and have 'static' in USE.
Fixed it to only build static if we are just building the C frontend.
