[gentoo-amd64] Re: Re: problems with gmp and portage

["Duncan" <1i5t5.duncan@cox.net>]

Kyle Liddell <kyle@foobox.homelinux.net> posted
20060706141513.GA14608@athlon.localdomain, excerpted below, on  Thu, 06
Jul 2006 09:15:13 -0500:

> So, I decided to give up and try doing an emerge -ep world to rebuild
> everything.  However, I get very similar errors when trying to build
> gettext.  Just for fun, I changed my profile to 2006.0/no-multilib, and I
> got the same errors.  Finally, in the spirit of really breaking things, I
> ran the bootstrap.sh script, but it died in the same way.
> 
> How do I fix my system now?

Well, it's at least consistent! <g>

I was hoping that the rebuild would correct the problem before it got to
anything affected by it, but it seems not.

Did you try a diff on the configure.log (config.log?) from the successful
non-portage run and the unsuccessful portage run?  As I said in a previous
response, with any luck at all, that should reveal the difference, and
from there it should be possible to work backward to what environmental
difference caused it.

For kicks, if you go back to stable portage (looks like 2.1-r1, from my
sync about 18 hours ago), does that fix it? What about going back to 2.0.5x
portage (2.0.54-r2, or 2.0.51.22-r3)?  Note that you should do an emerge
--metadata after reverting to 2.0.5x.



-- 
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

-- 
gentoo-amd64@gentoo.org mailing list