On 11/25/05, Harry Putnam <[EMAIL PROTECTED]> wrote: > Richard Fish <[EMAIL PROTECTED]> writes: > > > Ok, now we are going to need to see the output of emerge --info, > > because for some reason your toolchain thinks it is cross-compiling: > > There appears to be some confusion in that output as to what USE flags > are in force. > ACCEPT_KEYWORDS="x86 ~x86" > I guess the last is what is used? > > I have in /etc/make.conf > > ACCEPT_KEYWORDS="~x86" > This is because a few -u worls back (2 I think) I foolishly ran > ACCEPT_KEYWORDS='~x86' emerges -v -u -D world
Well, the only way ~x86 could have been added to make.conf was if it was edited directly. Running with ACCEPT_KEYWORDS in the environment would not have changed it. Having --info report both x86 and ~x86 is normal...it means both stable and testing packages are allowed. > > And it seems more trouble to back out of that now than to just try to > see if I (with help) can stay on top of it. Well, it isn't terribly difficult to switch back to stable. Just remove the ~x86 keyword from make.conf and "emerge -DNuv world". The worst case is when you have some testing package merged for which there is no stable version, in which case you either have to unmerge the package or add the appropriate entry to /etc/portage/package.keywords. And of course, don't forget etc-update afterwards. Anyway, on the to the problem at hand: > emerge -n -v --info 2>&1|tee emergeInfo.log > > Gentoo Base System version 1.6.13 Hmm, I would have expected something more recent for ~x86. What does "emerge -vp sys-apps/baselayout" report? > Portage 2.0.53_rc7 (default-linux/x86/2005.0, gcc-3.3.5-20050130, > glibc-2.3.5-r3, 2.6.14-gentoo-r2 i686) Ok, run "gcc-config -l". You should see an entry for i686-pc-linux-gnu-3.4.4. If so, run "gcc-config i686-pc-linux-gnu-3.4.4" Then try the revdep-rebuld again. Everything else looks sane. -Richard -- gentoo-user@gentoo.org mailing list
