Re: gcc 3.2 limits.h from crtstuff.c

[David Meggy <dmeggy at techsol dot ca>]

Ok, I tried just making a soft links for
$(my cross env)/arm-linux/sys-include to $(my cross env)/include
$(my cross env)arm-linux/include to $(my cross env)/include
$(my cross env)arm-linux/lib to $(my cross env)/lib

Which had exactly the same error.  Also when I try to add
--with-headers, gcc gives me the following message

*** --with-headers is only supported when cross compiling

Note: I'm trying to make a native compiler, using a cross compiler.

Dave

On Tue, 2002-09-03 at 01:43, Rupert Wood wrote:
> 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.
> 
> 
-- 
~~~~~~~~~~~~~~~~~~~~~~~~
     David Meggy
     Engineering

Technical Solutions Inc.
Unit #1 7157 Honeyman St
Delta BC Canada, V4G 1E2
     www.techsol.ca

eMail: dmeggy@techsol.ca
Tel: 604 946 TECH (8324)
Fax: 604 946 6445
~~~~~~~~~~~~~~~~~~~~~~~~