This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: gcc 3.2 limits.h from crtstuff.c
- From: Rupert Wood <rup at kanat dot pair dot com>
- To: David Meggy <dmeggy at techsol dot ca>
- Cc: <gcc-help at gcc dot gnu dot org>
- Date: Tue, 3 Sep 2002 04:43:27 -0400 (EDT)
- Subject: Re: gcc 3.2 limits.h from crtstuff.c
Dave Meggy wrote:
> I think there is something wrong with the way it finds includes.
I'm not on my usual system so I can't verify this, but from memory:
> According to my inserted #warnings ${my cross env}/include/limits.h
> is never called.
I've had disagreements in the past about where things should live, but I
think the headers should be in
$(my cross env)/arm-linux/sys-include
and libraries
$(my cross env)/arm-linux/lib
These are the paths used by GCC's configure's --with-headers and
--with-libs. Kai on the crossgcc list will tell you that the headers
should actually go in
$(my cross env)/arm-linux/include
but I think he's wrong :-)
> and the compiler I'm trying to build was configured like this
> {gcc_source_path}/configure --target=arm-linux --host=arm-linux \
> --build=i386-pc-linux-gnu --prefix=${my cross runtime env} \
> --enable-languages=c --disable-multilib \
> --disable-threads --disable-shared
Since you're neither specifying --with-headers or --with-libs (which is
fine if they're already in place) you need to specify --without-newlib.
Hope that helps,
Rup.