* What would cause combined build to not install std headers (newlib)?
@ 2007-12-05 21:41 Rick Mann
0 siblings, 0 replies; only message in thread
From: Rick Mann @ 2007-12-05 21:41 UTC (permalink / raw)
To: gcc-help
Hi. I've built (on Mac OS X 10.5) a combined binutils-2.17, gcc-4.2.1,
and newlib-1.15. With the following configure line, the build and
install seem to complete fine, but I get none of the standard headers
(like errno.h and stdio.h).
../combined/configure --prefix=$gPrefix --target=xscale-elf --enable-
languages=c,c++ --disable-nls --with-newlib --disable-libssp --disable-
newlib-supplied-syscalls
When I built it before, I didn't use --disable-newlib-supplied-
syscalls, and I got everything. I'm going to try again, but that'll
take a long time, and I need to use --disable-newlib-supplied-syscalls.
Am I missing something?
TIA,
Rick
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2007-12-05 21:41 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-12-05 21:41 What would cause combined build to not install std headers (newlib)? Rick Mann
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 read-only IMAP folder(s) and NNTP newsgroup(s).