* Re: egcs-1.1.2 build problems
[not found] <Pine.GSO.4.03.9903181139140.22956-100000@isis.ucolick.org>
@ 1999-03-19 6:54 ` Martin Costabel
0 siblings, 0 replies; only message in thread
From: Martin Costabel @ 1999-03-19 6:54 UTC (permalink / raw)
To: Patrik Jonsson; +Cc: linuxppc-dev@lists.linuxppc.org
Patrik Jonsson wrote:
>
> Hi all,
> I'm trying to build the latest egcs, but it fails with the following
> error:
>
> In file included from ../../../egcs-1.1.2/libio/iolibio.h:1,
> from ../../../egcs-1.1.2/libio/libioP.h:40,
> from ../../../egcs-1.1.2/libio/iogetline.c:26:
> ../../../egcs-1.1.2/libio/libio.h:168: stdio-lock.h: No such file or
> directory
>
> Where is the stdio-lock.h file supposed to come from?
It is supposed to be in /usr/include, but it is not there, because
glibc-1.99 is not quite glibc-2. If you have libg++-devel installed,
there is one in /usr/include/g++ which you could copy to /usr/include.
Or you could change the definition of __GLIBC__ from 2 to 1 in
/usr/include/features.h. This takes care of many of these "lying
glibc-961212" problems and introduces some others.
Or you could hack libio/libio.h to not include stdio-lock.h any more.
Or you could install pre-R5. This is what I have.
I don't know what those who compiled egcs-1.1.2 sucessfully under R4
were doing. I suppose Gary Thomas has a solution?
--
Martin
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~1999-03-19 6:54 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <Pine.GSO.4.03.9903181139140.22956-100000@isis.ucolick.org>
1999-03-19 6:54 ` egcs-1.1.2 build problems Martin Costabel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).