From: Craig Rodrigues <rodrigc@attbi.com>
To: gcc@gcc.gnu.org
Subject: Re: 3.2.2 c++ compile problems
Date: Mon, 23 Dec 2002 13:02:00 -0000 [thread overview]
Message-ID: <20021223150415.A8732@attbi.com> (raw)
In-Reply-To: <20021223115552.A31822@synopsys.com>; from jbuck@synopsys.com on Mon, Dec 23, 2002 at 11:55:52AM -0800
On Mon, Dec 23, 2002 at 11:55:52AM -0800, Joe Buck wrote:
> Craig, your patch seems to assume that the compiler will always be GCC:
> you test for GCC 3, and otherwise explicitly declare new and delete
> in the global namespace (which is correct only for GCC 2).
The Makefile for the sparky program is hardcoded to use GCC, and
probably won't work with anything besides GCC.
Yes, inverting the logic to test for GCC2 by default is easy to do.
--
Craig Rodrigues
http://www.gis.net/~craigr
rodrigc@attbi.com
prev parent reply other threads:[~2002-12-23 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-23 9:53 Jack Howarth
2002-12-23 10:11 ` Craig Rodrigues
2002-12-23 10:50 ` Jack Howarth
2002-12-23 11:24 ` Gabriel Dos Reis
2002-12-23 11:56 ` Craig Rodrigues
2002-12-23 13:02 ` Joe Buck
2002-12-23 13:02 ` Craig Rodrigues [this message]
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=20021223150415.A8732@attbi.com \
--to=rodrigc@attbi.com \
--cc=gcc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).