Gentoo Archives: gentoo-user

From: Meino Christian Cramer <Meino.Cramer@×××.de>
To: gentoo-user@l.g.o
Subject: [gentoo-user] /etc/make.conf: changing CHOST on same system
Date: Sat, 02 Sep 2006 04:53:30
Message-Id: 20060902.064253.74744032.Meino.Cramer@gmx.de
1 Hi,
2
3 I got some homebrewed problems :-/
4
5 This morning I tried to update to glibc-2.4-r3.
6 Checking dependencies breaks with:
7
8 ----------------------------------------------------------------------
9 >>> checking glibc-2.4-patches-1.17.tar.bz2 ;-)
10 >>> checking glibc-linuxthreads-20060605.tar.bz2 ;-)
11 >>> checking glibc-powerpc-cpu-addon-v0.01.tgz ;-)
12 glibc-2.4 is nptl-only!
13 NPTL requires a CHOST of i486 or better
14
15 !!! ERROR: sys-libs/glibc-2.4-r3 failed.
16 Call stack:
17 ebuild.sh, line 1555: Called dyn_setup
18 ebuild.sh, line 668: Called pkg_setup
19 glibc-2.4-r3.ebuild, line 1079: Called die
20
21 !!! please add USE='nptl nptlonly' to make.conf
22 !!! If you need support, post the topmost build error, and the call stack if relevant.
23
24 ----------------------------------------------------------------------
25
26
27 I added "nptl nptlonly" to my /etc/make.conf but the error (and the
28 suggestion to add "nptl nptlonly" to /etc/make.conf) remain.
29
30 BUT:
31 For my CHOST there is an entry in /etc/make.conf:
32 CHOST="i386-pc-linux-gnu"
33
34 So I think, that the checker script for glibc looks there and thought,
35 my system is running a i386 CPU, but it runs an
36 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+.
37
38 It seems my installation of gentoo, which I did months ago wasn't
39 completly correct, it does run fine since then, though.
40
41 My question is:
42 Is there a way (possibly another one then completly installing all
43 stuff from the beginning or to recompile all...) to correct my fault ?
44
45 Thank you very much for any help in advance !
46 Have a nice weekend!
47 mcc
48
49
50
51 --
52 gentoo-user@g.o mailing list

Replies

Subject Author
Re: [gentoo-user] /etc/make.conf: changing CHOST on same system Richard Fish <bigfish@××××××××××.org>