| 1 |
On 9/1/06, Meino Christian Cramer <Meino.Cramer@×××.de> wrote: |
| 2 |
> glibc-2.4 is nptl-only! |
| 3 |
> NPTL requires a CHOST of i486 or better |
| 4 |
|
| 5 |
You missed fixing this error. |
| 6 |
|
| 7 |
|
| 8 |
-Richard |
| 9 |
|
| 10 |
> |
| 11 |
> !!! ERROR: sys-libs/glibc-2.4-r3 failed. |
| 12 |
> Call stack: |
| 13 |
> ebuild.sh, line 1555: Called dyn_setup |
| 14 |
> ebuild.sh, line 668: Called pkg_setup |
| 15 |
> glibc-2.4-r3.ebuild, line 1079: Called die |
| 16 |
> |
| 17 |
> !!! please add USE='nptl nptlonly' to make.conf |
| 18 |
> !!! If you need support, post the topmost build error, and the call stack if relevant. |
| 19 |
> |
| 20 |
> ---------------------------------------------------------------------- |
| 21 |
> |
| 22 |
> |
| 23 |
> I added "nptl nptlonly" to my /etc/make.conf but the error (and the |
| 24 |
> suggestion to add "nptl nptlonly" to /etc/make.conf) remain. |
| 25 |
> |
| 26 |
> BUT: |
| 27 |
> For my CHOST there is an entry in /etc/make.conf: |
| 28 |
> CHOST="i386-pc-linux-gnu" |
| 29 |
> |
| 30 |
> So I think, that the checker script for glibc looks there and thought, |
| 31 |
> my system is running a i386 CPU, but it runs an |
| 32 |
> AMD Athlon(tm) 64 X2 Dual Core Processor 3800+. |
| 33 |
|
| 34 |
Yep, you will need to change your CHOST to i686-pc-linux-gnu to get |
| 35 |
the new glibc. |
| 36 |
|
| 37 |
> Is there a way (possibly another one then completly installing all |
| 38 |
> stuff from the beginning or to recompile all...) to correct my fault ? |
| 39 |
|
| 40 |
Nope. After changing CHOST, you need to emerge -e world. And I would |
| 41 |
keep a live CD close by just in case. |
| 42 |
|
| 43 |
Your other option is to mask glibc-2.4, and stick with 2.3. |
| 44 |
|
| 45 |
echo ">=sys-libs/glibc-2.4" >> /etc/portage/package.mask |
| 46 |
|
| 47 |
-Richard |
| 48 |
-- |
| 49 |
gentoo-user@g.o mailing list |
Archives