public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Meggy <dmeggy@techsol.ca>
To: gcc-help@gcc.gnu.org
Subject: gcc 3.2 limits.h from crtstuff.c
Date: Mon, 02 Sep 2002 15:11:00 -0000	[thread overview]
Message-ID: <1031004187.410.21.camel@DavidAsus> (raw)


Hi, I'm trying to cross compile a native compiler.  I think there is
something wrong with the way it finds includes.  My neccessary
information and errors are below.  When the #include <limits.h> is made
from tsystem.h, gcc should first try ${my cross env}/include/limits.h
right?  Well it using the one from ./include/limits.h.  So now that this
one is calling #include_next <limits.h>, gcc can't find anymore
limits.h.  According to my inserted #warnings ${my cross
env}/include/limits.h is never called.

If someone could help, it would be greatly appreciated.

Dave



My build environment consists of gcc 3.2 configured as follows
./configure --target=arm-linux --host=i386-pc-linux-gnu \
--enable-target-optspace --prefix=${my cross env} \
--enable-languages=c --disable-multilib --disable-threads \
--with-gnu-ld --disable-nls --disable-shared

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

I get the following error

make[3]: Leaving directory
`/home/david/working/arm-native/arm-linux-gcc/gcc/intl'
arm-linux-gcc -O2 -DIN_GCC    -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -isystem ./include  -I. -I.
-I/home/david/working/arm-native/gcc-3.2/gcc
-I/home/david/working/arm-native/gcc-3.2/gcc/.
-I/home/david/working/arm-native/gcc-3.2/gcc/config
-I/home/david/working/arm-native/gcc-3.2/gcc/../include  -g0
-finhibit-size-directive -fno-inline-functions -fno-exceptions  \
   -c /home/david/working/arm-native/gcc-3.2/gcc/crtstuff.c -DCRT_BEGIN
\
  -o crtbegin.o
In file included from
/home/david/working/arm-native/gcc-3.2/gcc/tsystem.h:84,
                 from
/home/david/working/arm-native/gcc-3.2/gcc/crtstuff.c:62:
include/limits.h:3:2: warning: #warning "DAVE:********I'm here"
In file included from include/limits.h:11,
                 from
/home/david/working/arm-native/gcc-3.2/gcc/tsystem.h:84,
                 from
/home/david/working/arm-native/gcc-3.2/gcc/crtstuff.c:62:
/home/david/techsol/arm-cross-v0.9/lib/gcc-lib/arm-linux/3.2/include/syslimits.h:7:25: no include path in which to find limits.h
make[2]: *** [crtbegin.o] Error 1


I put in the #warning into the file {build_dir}/gcc/include/limits.h so
I could tell which limits.h it was using.


-- 
~~~~~~~~~~~~~~~~~~~~~~~~
     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
~~~~~~~~~~~~~~~~~~~~~~~~

             reply	other threads:[~2002-09-02 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02 15:11 David Meggy [this message]
2002-09-03  1:43 ` Rupert Wood
2002-09-03  8:07   ` David Meggy
2002-09-03  8:53   ` David Meggy
2002-09-03  9:17   ` David Meggy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1031004187.410.21.camel@DavidAsus \
    --to=dmeggy@techsol.ca \
    --cc=gcc-help@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).