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

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

[Meino Christian Cramer]

Hi,

 I got some homebrewed problems :-/

 This morning I tried to update to glibc-2.4-r3.
 Checking dependencies breaks with:

----------------------------------------------------------------------
 >>> checking glibc-2.4-patches-1.17.tar.bz2 ;-)
 >>> checking glibc-linuxthreads-20060605.tar.bz2 ;-)
 >>> checking glibc-powerpc-cpu-addon-v0.01.tgz ;-)
     glibc-2.4 is nptl-only!
     NPTL requires a CHOST of i486 or better

 !!! 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+.

It seems my installation of gentoo, which I did months ago wasn't
completly correct, it does run fine since then, though.

My question is:
Is there a way (possibly another one then completly installing all
stuff from the beginning or to recompile all...) to correct my fault ?

Thank you very much for any help in advance !
Have a nice weekend!
mcc



-- 
gentoo-user@gentoo.org mailing list

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

[Richard Fish]

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

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

[Meino Christian Cramer]

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

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

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]

On Saturday 02 September 2006 10:58, Meino Christian Cramer wrote:
> 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

...?.

I guess you didn't follow this list too carefully the last couple of days... 
Anyway, no you shouldn't emerge -e world more than once!

1. Correct the CHOST in make.conf
2. Make sure the nptl and nptlonly use flags are enabled.
3. *If* you want to upgrade your profile in the near future this may be a good 
time to do so. This step is optional. You may have a look at [1] for more 
info about this.
4. Follow the gcc upgrade guide [2].

Following the gcc upgrade guide will upgrade glibc and pretty much everething 
else that isn't quite up to date during the emerge -e world. Make sure that 
you follow the "General Upgrade Instructions" carefully though.

[1] http://www.gentoo.org/doc/en/gentoo-upgrading.xml
[2] http://www.gentoo.org/doc/en/gcc-upgrading.xml
-- 
Bo Andresen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

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

[Meino Christian Cramer]

From: Bo Ørsted Andresen <bo.andresen@zlin.dk>
Subject: Re: [gentoo-user] /etc/make.conf: changing CHOST on same system
Date: Sat, 2 Sep 2006 11:30:55 +0200

> On Saturday 02 September 2006 10:58, Meino Christian Cramer wrote:
> > 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
> 
> ...?.
> 
> I guess you didn't follow this list too carefully the last couple of days... 
> Anyway, no you shouldn't emerge -e world more than once!
> 
> 1. Correct the CHOST in make.conf
> 2. Make sure the nptl and nptlonly use flags are enabled.
> 3. *If* you want to upgrade your profile in the near future this may be a good 
> time to do so. This step is optional. You may have a look at [1] for more 
> info about this.
> 4. Follow the gcc upgrade guide [2].
> 
> Following the gcc upgrade guide will upgrade glibc and pretty much everething 
> else that isn't quite up to date during the emerge -e world. Make sure that 
> you follow the "General Upgrade Instructions" carefully though.
> 
> [1] http://www.gentoo.org/doc/en/gentoo-upgrading.xml
> [2] http://www.gentoo.org/doc/en/gcc-upgrading.xml
> -- 
> Bo Andresen

Hi Bo !

 ...unfortunately I got stuck again.

 What I did:
 Changed CHOST from i386* i686*, ensure that nptl and nptlonly are USEd.
 (I am running an AMD Athlon(tm) 64 X2 Dual Core Processor 3800+)

 emerge -uav gcc

 The result was:
 The first package (it was not the gcc), what was tried to compile, failed with
 "Compiler cannot create output" (or similiar, dont remember
 exactly...)

 Looks like, as the new CHOST results in looking for 
 /usr/lib/gcc/i686-pc-linux-gnu (which is not existing) instead of 
 /usr/lib/gcc/i386-pc-linux-gnu (which still does exist).

 Ok, but when I reset CHOST to i386* again, the new glibc will fail to
 compile, since it insist of haveing a CPU better then i386* (which
 was the inital reason for posting my problems.)

 Do I have a "recursive Armageddon" here ?

 Since I will replace gcc, would it be a soultion to rename all
 occurences of i386-pc-linux-gnu in my root directory tree with
 i686-pc-linux-gnu ??? Or symlink it? Or do I shoot myself just in my
 other foot this way?
 I know that this "solution" would be not gentleman like but a hack of a
 rookie...but...when gentlemen does not succeed ??? ;)

 By the way:
 I looked for sane CFLAGS for my CPU by best performance.
 I am not sure for the -msse3 flag...
 The docs say: You can enable -msse3 for the CPU (mentioned above)
 when the "pni" entry is in /proc/cpuinfo (which is in my case). On
 the other side /proc/cpuinfo mentioned sse and sse2 but not sse3:
 
   processor       : 0
   vendor_id       : AuthenticAMD
   cpu family      : 15
   model           : 43
   model name      : AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
   stepping        : 1
   cpu MHz         : 2002.999
   cache size      : 512 KB
   physical id     : 0
   siblings        : 2
   core id         : 0
   cpu cores       : 2
   fdiv_bug        : no
   hlt_bug         : no
   f00f_bug        : no
   coma_bug        : no
   fpu             : yes
   fpu_exception   : yes
   cpuid level     : 1
   wp              : yes
   flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
           cmov pat pse36 clflush mmx fxsr #sse# #sse2# ht syscall nx
           mmxext fxsr_opt lm 3dnowext 3dnow #pni# lahf_lm cmp_legacy ts
           fid vid ttp
   bogomips        : 4012.21
 
 Same goes for processor 1, but with slightly different bogomips
 (Sometimes even identical things seems to be different... ;O) .

 I dont know, how to get the information, whether my CPU has a
 Winchester, Manchester, Venice or whatever die...

 Last thing:
 When the gentoo docs talk about "AMD64" without mentioning, whether
 it is meant a 32bit- or 64bit-system....is it valid for 32bit AND
 64bit or only 64bit or...
 Sometimes I am not sure whether the docs are talking about "my
 system" since I am running a AMD64 -- a 64bit CPU -- in 32bit mode.


 Thanks a lot in advance for any help out of my homebrewed disaster...
 Keep hacking!
 mcc

-- 
gentoo-user@gentoo.org mailing list