i recompiled gcc and used portage and that worked. i think that mine is a paludis bug. i'll post the bug on the paludis bugzilla. thanks for your help anyway.
2007/10/18, Duncan <[EMAIL PROTECTED]>: > > Beso <[EMAIL PROTECTED]> posted > [EMAIL PROTECTED], excerpted > below, on Wed, 17 Oct 2007 23:19:40 +0200: > > > i've used the 25th comment command. i've moved the indicated files to a > > backup dir and then done a gcc-config -f x86_64-pc-linux-gnu-4.1.2 and > > retried compiling glibc but no luck. i've tried with an older version > > and by disabling and enabling ccache but i had no luck. > > If you used the 25th comment command, then you probably got some bad > hits, which would explain why moving them didn't help. Since you say > it's a pretty new system and has never had eselect compiler on it, it's > gotta be a different problem for you. > > Good luck. I'd suggest checking glibc bugs now, and filing one of your > own if you don't find one similar. > > I'm just glad I was able to get rid of such problems entirely, by going > 64-bit only (no-multilib profile). If you can't, you can't, but it's > sure nice when you can. =8^) > > -- > 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 > > -- > [EMAIL PROTECTED] mailing list > > -- dott. ing. beso
