| 1 |
kristina clair wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> I'm trying to update glibc with nptl and nptlonly USE flags, but I'm |
| 5 |
> getting an error. |
| 6 |
> |
| 7 |
> The emerge command I'm running is: |
| 8 |
> emerge --newuse -buD glibc |
| 9 |
> |
| 10 |
> The error is: |
| 11 |
> |
| 12 |
>>>>Install glibc-2.3.4.20041102-r1 into |
| 13 |
> |
| 14 |
> /var/tmp/portage/glibc-2.3.4.20041102-r1/image/ category sys-libs |
| 15 |
> /usr/portage/sys-libs/glibc/glibc-2.3.4.20041102-r1.ebuild: line 845: |
| 16 |
> cd: /var/tmp/portage/glibc-2.3.4.20041102-r1/work/build-default-i386-pc-linux-gnu-nptl: |
| 17 |
> No such file or directory |
| 18 |
> * Installing GLIBC with NPTL... |
| 19 |
> Makeconfig:84: x86/config.make: No such file or directory |
| 20 |
> Makerules:782: no file name what ifor `include' |
| 21 |
> configure.in > configure.new |
| 22 |
> /bin/sh: configure.in: command not found |
| 23 |
> make: *** [configure] Error 127 |
| 24 |
> |
| 25 |
> Everything I've read about ntpl and glibc would seem to indicate that |
| 26 |
> I should just be able to emerge a new glibc without any problems. Any |
| 27 |
> ideas? |
| 28 |
> |
| 29 |
> Thanks, |
| 30 |
> Kristina |
| 31 |
> |
| 32 |
|
| 33 |
That default-i386-pc-linux-gnu-nptl looks suspicious because with nptl CHOST is restricted to i486|i586|i686-pc-linux-gnu. What is your CHOST? |
| 34 |
|
| 35 |
Zac |
| 36 |
-- |
| 37 |
gentoo-user@g.o mailing list |
Archives