problem compiling gcc-2.95.3 with BLFS instructions using 2.6.2/NPTL

Allard Welter allard at
Fri Jan 30 11:38:14 PST 2004

On Thursday 29 January 2004 15:37, Michael Beuse wrote:
> Hi folks,
> got some problems while compiling gcc-2.95.3 with c and c++ compiler.
> I am using the BLFS instructions out of the current CVS-Version.
> He's complaining about a missing lowlevellock.h.
> The complete compile log is attached.
> I hope some can help me out.
> Thanks for your help,
> 	Michael Beuse

In file included from ../../../gcc-2.95.3/libio/libio.h:167,
                 from ../../../gcc-2.95.3/libio/iolibio.h:1,
                 from ../../../gcc-2.95.3/libio/libioP.h:47,
                 from ../../../gcc-2.95.3/libio/iogetline.c:26:
/usr/include/bits/stdio-lock.h:24: lowlevellock.h: Datei oder Verzeichnis 
nicht gefunden
make[2]: *** [iogetline.o] Fehler 1
make[2]: Leaving directory `/usr/src/sources/gcc-build/i686-pc-linux-gnu/
make[1]: *** [all-target-libio] Fehler 2
make[1]: Leaving directory `/usr/src/sources/gcc-build'
make: *** [bootstrap] Fehler 2

Above the last part of the error.
This has me puzzled. I've looked at the headers installed by glibc-2.3.2, 
there is no #include <lowlevellock.h> in the header stdio-lock.h however in 
the cvs glibc there is, but no lowlevellock.h header is installed. I just 
happen to be busy with a new lfs install so I could compare. I haven't done 
any googling yet or looked much further into it. This post has gone so long 
w/o reply that I thought I'd have a preliminary look.

If you still have the glibc sources around, try copying the following file 
into /usr/include


(assuming of course you're on a x86 architecture) There's no other exotic 
includes in this file, so things should work. I wasn't intending to install 
gcc-2.95.3, but have now changed my mind. Will report if I find anything 

Regards - Allard.

allard at

More information about the lfs-support mailing list