> > I'm trying to update glibc with nptl and nptlonly USE flags, but I'm > > getting an error. > > > > The emerge command I'm running is: > > emerge --newuse -buD glibc > > > > The error is: > > > >>>>Install glibc-2.3.4.20041102-r1 into > > > > /var/tmp/portage/glibc-2.3.4.20041102-r1/image/ category sys-libs > > /usr/portage/sys-libs/glibc/glibc-2.3.4.20041102-r1.ebuild: line 845: > > cd: > > /var/tmp/portage/glibc-2.3.4.20041102-r1/work/build-default-i386-pc-linux-gnu-nptl: > > No such file or directory > > * Installing GLIBC with NPTL... > > Makeconfig:84: x86/config.make: No such file or directory > > Makerules:782: no file name what ifor `include' > > configure.in > configure.new > > /bin/sh: configure.in: command not found > > make: *** [configure] Error 127 > > > > Everything I've read about ntpl and glibc would seem to indicate that > > I should just be able to emerge a new glibc without any problems. Any > > ideas? > > > > Thanks, > > Kristina > > > > 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?
Hm! CFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer" CHOST="i386-pc-linux-gnu" I did not set this box up, so I'm not sure - is there any reason why someone would set the CHOST to that? I checked the /var/tmp/portage/glibc-2.3.4.20041102-r1/work directory, and indeed there is no subdirectory build-default-i386-pc-linux-gnu-nptl. In fact, in the work directory, there is only glibc-2.3.3. Thanks, Kristina -- gentoo-user@gentoo.org mailing list
