On Wed, Sep 17, 2003 at 05:44:46PM +0900, Jason Stubbs wrote: > On Wednesday 17 September 2003 15:52, Jason Stubbs wrote: > > On Wednesday 17 September 2003 15:38, Andy Smith wrote: > > > Hmm. So it's quite likely that gcc is the culprit here. Yet that > > > newly installed gcc does seem to work; I can compile things. > > > > gcc-3.3.1-r2 has some bugs. Check on bugzilla. There's also been a bit of > > mention of gentoo-dev. > > It's also mentioned in the forums. Check this thread for downloading a working > version: http://forums.gentoo.org/viewtopic.php?t=84803
Jason, you're a life saver, thanks! I followed the suggested workaround of moving libgcc_s.a in http://forums.gentoo.org/viewtopic.php?t=84803&postdays=0&postorder=asc&start=25&sid=28c4e3c9a33ac8d51fc7a94ce5e6a3c1 - this made my gcc work. I then manually unpacked python and installed it, and it worked. Then the rescue archive of portage allowed me to get a working portage. I am now in the process of merging a working version of gcc, then python, and then I guess I should do my whole system. In light of this unfortunate incident, is there any easy way to choose ebuilds from ~x86 in general, but from x86 for some specific ebuilds that should "never be allowed to break"? I am thinking binutils, gcc, python, portage for example. I'm happy for my web browsers, irc clients and what not to be bleeding edge but unstable, but it kind of ruins my day when I merge a broken gcc that recompiles half my system and breaks it. -- [EMAIL PROTECTED] mailing list
