public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Meggy <dmeggy@techsol.ca>
To: Rupert Wood <rup@kanat.pair.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc 3.2 limits.h from crtstuff.c
Date: Tue, 03 Sep 2002 08:53:00 -0000	[thread overview]
Message-ID: <1031067927.410.22.camel@DavidAsus> (raw)
In-Reply-To: <Pine.BSF.4.30.0209030442290.1320-100000@kanat.pair.com>


I'm pretty sure there is something wrong with isystem, #include_next.

According to the gcc manual
-isystem dir
    Search dir for header files, after all directories specified by -I
but before the standard system directories. Mark it as a system
directory, so that it gets the same special treatment as is applied to
the standard system directories.

Which is correct so #include_next should get the C-lib version.  Which I
know it finds normally because the following program works.

#include <limits.h>
int main() { return 0; }

and when I enter a #warning statement inside the c-lib limits.h it finds
it. eg.
~/tmp$ arm-linux-gcc Dave.c
In file included from Dave.c:1:
/home/david/techsol/arm-cross-v0.9/include/limits.h:22:2: warning:
#warning Dave:C-lib limits.h 


Dave


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

  parent reply	other threads:[~2002-09-03 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02 15:11 David Meggy
2002-09-03  1:43 ` Rupert Wood
2002-09-03  8:07   ` David Meggy
2002-09-03  8:53   ` David Meggy [this message]
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=1031067927.410.22.camel@DavidAsus \
    --to=dmeggy@techsol.ca \
    --cc=gcc-help@gcc.gnu.org \
    --cc=rup@kanat.pair.com \
    /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).