Newlib build error on ix86-linux

J. Johnston
Sat Jun 21 18:43:00 GMT 2003

Jose Miguel Goncalves wrote:
>>> Jeff,
>>> I've followed your advice and give an absolute path to configure
>>> Unfortunely the build stiil aborts, now in another place:
>>> gcc 
>>> -I/home/jmpg/newlib-cvs/build/i686-pc-linux-gnu/newlib/targ-include 
>>> -I/home/jmpg/newlib-cvs/src/newlib/./libc/include 
>>> -DPACKAGE=\"newlib\" -DVERSION=\"1.11.0\" -I. 
>>> -I/home/jmpg/newlib-cvs/src/newlib/libc/stdio -O2 -DMB_CAPABLE -Wall 
>>> -O2 -g -O2 -O2 -g -O2 -c 
>>> /home/jmpg/newlib-cvs/src/newlib/libc/stdio/findfp.c  -fPIC -DPIC -o 
>>> .libs/findfp.o
>>> In file included from 
>>> /home/jmpg/newlib-cvs/build/i686-pc-linux-gnu/newlib/targ-include/sys/lock.h:7, 
>>>                  from 
>>> /home/jmpg/newlib-cvs/src/newlib/libc/stdio/findfp.c:25:
>>> /usr/include/bits/libc-lock.h:27:36: linuxthreads/internals.h: No 
>>> such file or directory
>>> make[4]: *** [findfp.lo] Error 1
>>> José Gonçalves
>> What level of glibc are you using?  Newlib turns on the _LIBC flag to get
>> some special definitions but this flag is used for building glibc and
>> header files are within their rights to expect to drag things in the 
>> from the glibc
>> sources.  Meshing newlib and glibc header files so they work in 
>> harmony will be an
>> on-going job.  Can you send me a copy of your 
>> /usr/include/bits/libc-lock.h?
>> -- Jeff J.
> Jeff,
> I'm using glibc 2.3.1.
> I attach my "/usr/include/bits/libc-lock.h" header file.
> José

Ok, Jose.  I need to do some work to make it work with glibc 2.3.1.  The header
files have changed.  Getting newlib and glibc header files coexisting is an on-going
struggle.  I have a few tweaks allowing it to go further, but I have uncovered some
other problems due to newer glibc headers.  I will hopefully have something
to post to you later today.

-- Jeff J.

More information about the Newlib mailing list