From: Hans-Peter Nilsson <hp@bitrange.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Nick Clifton <nickc@redhat.com>,
binutils@sources.redhat.com, gdb-patches@sources.redhat.com,
newlib@sources.redhat.com, dejagnu@gnu.org
Subject: Re: Dejagnu: use -isystem to include system header files.
Date: Fri, 12 Nov 2004 00:25:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.58.0411111833020.25702@dair.pair.com> (raw)
In-Reply-To: <20041111142237.GA25841@nevyn.them.org>
Yay cross-posting! I helped by adding a list!
On Thu, 11 Nov 2004, Daniel Jacobowitz wrote:
> On Thu, Nov 11, 2004 at 11:58:15AM +0000, Nick Clifton wrote:
> > Hi Guys,
> >
> > I am going to check in the attached patch which imports a fix from
> > the mainline dejagnu sources. This fix is to use the -isystem
> > switch to include system header files rather than -I. This fixes
> > several unexpected failures in the GCC and G++ testsuites where the
> > newlib system header file <limits.h> is included in strict ANSI
> > mode, and the compiler barfs on the #include_next directive.
>
> This patch will break in-tree testing for yet other targets.
But presumably only for old broken systems: no non-obsolete
system should need to fake an extern "C" as is done when *not*
defining NO_IMPLICIT_EXTERN_C; they should all be C++-aware.
> I believe
> arm-elf was affected - anything which does not set
> NO_IMPLICIT_EXTERN_C.
Bug in the arm-elf port: it should define NO_IMPLICIT_EXTERN_C.
Sounds like there's a bug in the -isystem interaction with
NO_IMPLICIT_EXTERN_C too. (Like, always assume
NO_IMPLICIT_EXTERN_C for all passed -isystem options aka.
never fake 'extern "C"' for path-options given on the command
line.)
> I discussed this with H-P on the dejagnu list
> but never figured out a solution, but...
Wot, there was no closure? For the record, the original email:
<URL:http://lists.gnu.org/archive/html/bug-dejagnu/2002-10/msg00009.html>
(the reply was in 2002-11). Our later conversation is at
<URL:http://lists.gnu.org/archive/html/dejagnu/2004-05/msg00003.html>.
I thought we had closure at
<URL:http://lists.gnu.org/archive/html/dejagnu/2004-05/msg00007.html>
or at least at
<URL:http://lists.gnu.org/archive/html/dejagnu/2004-05/msg00011.html>
but now that you bring it up, I just think it's more of a bug in
the arm-elf port and non-NO_IMPLICIT_EXTERN_C targets should be
xfailed for applicable tests. ;-)
> > * lib/libgloss.exp (newlib_include_flags): Use -isystem, not -I.
> > (libio_include_flags, g++_include_flags, libstdc++_include_flags,
> > winsup_include_flags): Ditto.
>
> ... I strongly suspect that g++ and winsup should be left out.
Mh, a bit spurious. Only actual C++ include directories could
be badly affected by non-NO_IMPLICIT_EXTERN_C-ness.
brgds, H-P
next prev parent reply other threads:[~2004-11-12 0:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 11:54 Nick Clifton
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 [this message]
2004-11-12 0:29 ` Daniel Jacobowitz
2004-11-12 1:29 ` Zack Weinberg
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
2004-11-18 20:07 Richard Earnshaw
2004-11-22 14:05 ` Nick Clifton
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=Pine.BSF.4.58.0411111833020.25702@dair.pair.com \
--to=hp@bitrange.com \
--cc=binutils@sources.redhat.com \
--cc=dejagnu@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=newlib@sources.redhat.com \
--cc=nickc@redhat.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).