From: Daniel Jacobowitz <drow@false.org>
To: Hans-Peter Nilsson <hp@bitrange.com>
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:29:00 -0000 [thread overview]
Message-ID: <20041112002755.GA7143@nevyn.them.org> (raw)
In-Reply-To: <Pine.BSF.4.58.0411111833020.25702@dair.pair.com>
On Thu, Nov 11, 2004 at 07:25:19PM -0500, Hans-Peter Nilsson wrote:
> Bug in the arm-elf port: it should define NO_IMPLICIT_EXTERN_C.
Zack's been wanting to flip the default for NO_IMPLICIT_EXTERN_C for
ages. But until that's been done - and done for a couple of years
- let's try to accomodate this in DejaGNU, OK :-)
> 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. ;-)
There was closure that I needed to go try something, which I never got
around to :-)
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-11-12 0:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2004-11-12 1:30 ` 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=20041112002755.GA7143@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sources.redhat.com \
--cc=dejagnu@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=hp@bitrange.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