Duncan <[email protected]> posted [email protected], excerpted below, on Wed, 28 Jan 2009 14:30:10 +0000:
> Thanks. BTW, gcc-4.3.3 is out now. I've upgraded but not tried it yet, > tho I will be trying it quite a bit shortly, merging KDE 4.2. FWIW, if you merged /any/ gcc (stable or unstable) early today (28th) and going back an unknown but reasonably limited time), you likely merged while toolchain.eclass has a bug that caused some of gcc's *.la files to have an incorrect path. There were in fact several other toolchain.eclass changes today (I checked the logs while working the above bug), so several other bugs may have occurred and been fixed as well. AFAIK, the bugs are fixed now. I know the one I was struck with is fixed. So anyone who has merged a gcc over the last week (say), may wish to remerge it, just to be sure. Either that or simply keep this in mind and if you see errors involving libgomp.la, /then/ remerge gcc. That's the bug that hit me. Again, this bug was NOT with any particular gcc version or its ebuild, but with an eclass (toolchain.eclass) all the gcc ebuilds use. Thus, it will have affected... probably any gcc merged while the bug was active. It will have certainly affected any with libgomp.la, so at least the gcc:4.2 and gcc:4.3 slots I have merged here, according to equery b libgomp.la. Doing a sync and remerging the gcc in question should fix the issue, as the eclass is now fixed. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
