Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Richard Earnshaw" <Richard.Earnshaw@arm.com>
To: "Nick Clifton" <nickc@redhat.com>,
	"Richard Earnshaw" <rearnsha@gcc.gnu.org>
Cc: <binutils@sources.redhat.com>, <gdb-patches@sources.redhat.com>,
	<newlib@sources.redhat.com>
Subject: RE: Dejagnu: use -isystem to include system header files.
Date: Thu, 18 Nov 2004 20:07:00 -0000	[thread overview]
Message-ID: <89A528FE6DB0FA44877BB2F05B8467180160F913@ZIPPY.Emea.Arm.com> (raw)

> > I think the gcc/include directory must be added implicitly 
> from the -B
> > option.  It would appear that these add -isystem type include
> > directories, so it might be just a matter of ordering the -B and
> > -isystem options appropriately.
> 
> But - how would this help in the situation where -ansi and -pedantic 
> have been specified as well.  In those cases we do not want 
> to get the 
> limits.h file from newlib.

The issue wasn't really about picking up gcc/include/limits.h over
newlib/include/limits.h, it was about how we processed the newlib
version when in strict ANSI mode.  That should be handled correctly when
we use -isystem (because that relaxes the rules).  So I think we should
try and get the search order back to what it was before, but when still
using -isystem.

R.


             reply	other threads:[~2004-11-18 20:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 20:07 Richard Earnshaw [this message]
2004-11-22 14:05 ` Nick Clifton
  -- strict thread matches above, loose matches on Subject: below --
2004-11-17 17:47 Richard Earnshaw
2004-11-18  9:15 ` Nick Clifton
2004-11-18 11:15   ` Richard Earnshaw
2004-11-18 15:56     ` Nick Clifton
     [not found] <m3pt2koaw8.fsf@redhat.com>
2004-11-11 14:22 ` Daniel Jacobowitz
2004-11-11 15:54   ` Nick Clifton
2004-11-11 17:00     ` Daniel Jacobowitz
2004-11-12  0:25   ` Hans-Peter Nilsson
2004-11-12  0:29     ` Daniel Jacobowitz
2004-11-12  1:30       ` Zack Weinberg

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=89A528FE6DB0FA44877BB2F05B8467180160F913@ZIPPY.Emea.Arm.com \
    --to=richard.earnshaw@arm.com \
    --cc=binutils@sources.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=newlib@sources.redhat.com \
    --cc=nickc@redhat.com \
    --cc=rearnsha@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