From: Mark Kettenis <kettenis@chello.nl>
To: cagney@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Add IBM's C problem to news
Date: Fri, 11 Jun 2004 11:13:00 -0000 [thread overview]
Message-ID: <200406111113.i5BBDCJP000953@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <40C93752.5080102@gnu.org> (message from Andrew Cagney on Fri, 11 Jun 2004 00:38:42 -0400)
Date: Fri, 11 Jun 2004 00:38:42 -0400
From: Andrew Cagney <cagney@gnu.org>
I'll commit this tomorrow,
2004-06-11 Andrew Cagney <cagney@gnu.org>
* NEWS: Mention fix for IBM's C compiler.
* Fixed build problems when using IBM's C compiler.
The files bfd/elf-bfd.h, gdb/dictionary.c and gdb/types.c contained
non ISO-C code that stopped them being compiled by IBM's ISO-C
compiler.
The IBM C compiler is just an example of a compiler that chockes in
the GCC-isms that were removed. Can you make the entry a bit more
neutral?
Mark
next prev parent reply other threads:[~2004-06-11 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 4:38 Andrew Cagney
2004-06-11 11:13 ` Mark Kettenis [this message]
2004-06-11 18:56 ` Andrew Cagney
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=200406111113.i5BBDCJP000953@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.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