| 1 |
From: "Richard Fish" <bigfish@××××××××××.org> |
| 2 |
Subject: Re: [gentoo-user] /etc/make.conf: changing CHOST on same system |
| 3 |
Date: Fri, 1 Sep 2006 22:38:38 -0700 |
| 4 |
|
| 5 |
> On 9/1/06, Meino Christian Cramer <Meino.Cramer@×××.de> wrote: |
| 6 |
> > glibc-2.4 is nptl-only! |
| 7 |
> > NPTL requires a CHOST of i486 or better |
| 8 |
> |
| 9 |
> You missed fixing this error. |
| 10 |
> |
| 11 |
> |
| 12 |
> -Richard |
| 13 |
> |
| 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 |
> Yep, you will need to change your CHOST to i686-pc-linux-gnu to get |
| 39 |
> the new glibc. |
| 40 |
> |
| 41 |
> > Is there a way (possibly another one then completly installing all |
| 42 |
> > stuff from the beginning or to recompile all...) to correct my fault ? |
| 43 |
> |
| 44 |
> Nope. After changing CHOST, you need to emerge -e world. And I would |
| 45 |
> keep a live CD close by just in case. |
| 46 |
> |
| 47 |
> Your other option is to mask glibc-2.4, and stick with 2.3. |
| 48 |
> |
| 49 |
> echo ">=sys-libs/glibc-2.4" >> /etc/portage/package.mask |
| 50 |
> |
| 51 |
> -Richard |
| 52 |
> -- |
| 53 |
> gentoo-user@g.o mailing list |
| 54 |
> |
| 55 |
|
| 56 |
Hi Richard, |
| 57 |
|
| 58 |
sigh...I feared that... :-/ |
| 59 |
|
| 60 |
So, is it correct / necessary in my case to do the following for |
| 61 |
upgrading to gcc-4.1: |
| 62 |
|
| 63 |
Correct the CHOST fault |
| 64 |
emerge -e world |
| 65 |
emerge glibc |
| 66 |
emerge -e world |
| 67 |
emerge gcc |
| 68 |
emerge -e world |
| 69 |
|
| 70 |
(and when finished, my computer is outdated...) |
| 71 |
|
| 72 |
What incompatibilities will I face, when finally gcc-4.1 is running ? |
| 73 |
Is there a list of "working" and "not-working" things ??? |
| 74 |
|
| 75 |
Keep hacking! |
| 76 |
mcc |
| 77 |
|
| 78 |
-- |
| 79 |
gentoo-user@g.o mailing list |
Archives