* include paths and gcc-3.0.4
@ 2002-04-02 17:23 David Caldwell
0 siblings, 0 replies; only message in thread
From: David Caldwell @ 2002-04-02 17:23 UTC (permalink / raw)
To: gcc-help
Hello all,
First off: gcc version 3.0.4, newlib version 1.10.0.
I'm having a bunch of problems with include paths. I'm trying to make a
cross-compiler for arm-elf (for an embedded project). The problem is that
I'm using newlib, but gcc keeps insisting on making the default include
path "/usr/include" which is clearly wrong as newlib doesn't even install
its include stuff there. Newlib's includes get put into
/usr/local/arm-elf/include. So to get my stuff to compile at the moment I
have to pass "-I- -I /usr/local/arm-elf/include" to gcc which is really
gross (not to mention non-portable).
I have tried configuring with the following options (in various
combinations with various different values) and I have had no luck in
getting gcc to find the headers.
--prefix=/usr/local
--with-gxx-include-dir=/usr/local/arm-elf/include/g++-v3
--includedir=/usr/local/arm-elf/include
--with-headers=/$(gcc_source)/gcc/gincludes
CROSS_INCLUDE_DIR looks promising but I can't figure out how to cleanly set
it. It defaults to /usr/local/arm-elf/sys-include which is not where newlib
goes.
So, three questions:
* How do I get gcc to search the correct place by default?
* Can I put the "-I" junk in the specs file?
* Why doesn't this just work by default?
Thanks,
David
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2002-04-03 1:23 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-04-02 17:23 include paths and gcc-3.0.4 David Caldwell
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).