Re: [gentoo-user] /etc/make.conf: changing CHOST on same system

[Meino Christian Cramer <Meino.Cramer@gmx.de>]

From: "Richard Fish" <bigfish@asmallpond.org>
Subject: Re: [gentoo-user] /etc/make.conf: changing CHOST on same system
Date: Fri, 1 Sep 2006 22:38:38 -0700

> On 9/1/06, Meino Christian Cramer <Meino.Cramer@gmx.de> wrote:
> >      glibc-2.4 is nptl-only!
> >      NPTL requires a CHOST of i486 or better
> 
> You missed fixing this error.
> 
> 
> -Richard
> 
> >
> >  !!! ERROR: sys-libs/glibc-2.4-r3 failed.
> >  Call stack:
> >   ebuild.sh, line 1555:   Called dyn_setup
> >   ebuild.sh, line 668:   Called pkg_setup
> >   glibc-2.4-r3.ebuild, line 1079:   Called die
> >
> > !!! please add USE='nptl nptlonly' to make.conf
> > !!! If you need support, post the topmost build error, and the call stack if relevant.
> >
> > ----------------------------------------------------------------------
> >
> >
> > I added "nptl nptlonly" to my /etc/make.conf but the error (and the
> > suggestion to add "nptl nptlonly" to /etc/make.conf) remain.
> >
> > BUT:
> > For my CHOST there is an entry in /etc/make.conf:
> > CHOST="i386-pc-linux-gnu"
> >
> > So I think, that the checker script for glibc looks there and thought,
> > my system is running a i386 CPU, but it runs an
> > AMD Athlon(tm) 64 X2 Dual Core Processor 3800+.
> 
> Yep, you will need to change your CHOST to i686-pc-linux-gnu to get
> the new glibc.
> 
> > Is there a way (possibly another one then completly installing all
> > stuff from the beginning or to recompile all...) to correct my fault ?
> 
> Nope.  After changing CHOST, you need to emerge -e world.  And I would
> keep a live CD close by just in case.
> 
> Your other option is to mask glibc-2.4, and stick with 2.3.
> 
> echo ">=sys-libs/glibc-2.4" >> /etc/portage/package.mask
> 
> -Richard
> -- 
> gentoo-user@gentoo.org mailing list
> 

Hi Richard,

 sigh...I feared that... :-/

 So, is it correct / necessary in my case to do the following for
 upgrading to gcc-4.1:

 Correct the CHOST fault
 emerge -e world
 emerge glibc
 emerge -e world 
 emerge gcc
 emerge -e world

 (and when finished, my computer is outdated...)

 What incompatibilities will I face, when finally gcc-4.1 is running ?
 Is there a list of "working" and "not-working" things ???

 Keep hacking!
 mcc

-- 
gentoo-user@gentoo.org mailing list