1 |
> > I'm trying to update glibc with nptl and nptlonly USE flags, but I'm |
2 |
> > getting an error. |
3 |
> > |
4 |
> > The emerge command I'm running is: |
5 |
> > emerge --newuse -buD glibc |
6 |
> > |
7 |
> > The error is: |
8 |
> > |
9 |
> >>>>Install glibc-2.3.4.20041102-r1 into |
10 |
> > |
11 |
> > /var/tmp/portage/glibc-2.3.4.20041102-r1/image/ category sys-libs |
12 |
> > /usr/portage/sys-libs/glibc/glibc-2.3.4.20041102-r1.ebuild: line 845: |
13 |
> > cd: /var/tmp/portage/glibc-2.3.4.20041102-r1/work/build-default-i386-pc-linux-gnu-nptl: |
14 |
> > No such file or directory |
15 |
> > * Installing GLIBC with NPTL... |
16 |
> > Makeconfig:84: x86/config.make: No such file or directory |
17 |
> > Makerules:782: no file name what ifor `include' |
18 |
> > configure.in > configure.new |
19 |
> > /bin/sh: configure.in: command not found |
20 |
> > make: *** [configure] Error 127 |
21 |
> > |
22 |
> > Everything I've read about ntpl and glibc would seem to indicate that |
23 |
> > I should just be able to emerge a new glibc without any problems. Any |
24 |
> > ideas? |
25 |
> > |
26 |
> > Thanks, |
27 |
> > Kristina |
28 |
> > |
29 |
> |
30 |
> 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? |
31 |
|
32 |
Hm! |
33 |
CFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer" |
34 |
CHOST="i386-pc-linux-gnu" |
35 |
|
36 |
I did not set this box up, so I'm not sure - is there any reason why |
37 |
someone would set the CHOST to that? |
38 |
|
39 |
I checked the /var/tmp/portage/glibc-2.3.4.20041102-r1/work directory, |
40 |
and indeed there is no subdirectory |
41 |
build-default-i386-pc-linux-gnu-nptl. In fact, in the work directory, |
42 |
there is only glibc-2.3.3. |
43 |
|
44 |
Thanks, |
45 |
Kristina |
46 |
|
47 |
-- |
48 |
gentoo-user@g.o mailing list |