From: Joern Rennecke <amylaar@cygnus.co.uk>
To: jbuck@Synopsys.COM (Joe Buck)
Cc: ghazi@caip.rutgers.edu, mrs@wrs.com, robertlipe@usa.net,
egcs@cygnus.com, law@cygnus.com
Subject: Re: autoconf between stages. was: java fails to build
Date: Fri, 29 Jan 1999 19:08:00 -0000 [thread overview]
Message-ID: <199901300306.DAA08224@phal.cygnus.co.uk> (raw)
In-Reply-To: <199901292209.OAA08414@atrus.synopsys.com>
> Actually, it would be safe to use autoconf to determine compiler
> characteristics, but only to pay attention to its results when the
> compiler is not gcc. That is, include the autoconf-generated ones,
> but then append something like
>
> #ifdef __GNUC__
> ... undef certain autoconf-symbols
> ... define them to the a value appropriate for gcc
> #endif
That is safe only if the feature is available in all versions of gcc.
next prev parent reply other threads:[~1999-01-29 19:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-29 13:55 Kaveh R. Ghazi
1999-01-29 14:13 ` Joe Buck
1999-01-29 19:08 ` Joern Rennecke [this message]
1999-01-29 19:11 ` Joe Buck
1999-01-29 19:34 ` Joern Rennecke
-- strict thread matches above, loose matches on Subject: below --
1999-01-31 12:28 Kaveh R. Ghazi
1999-01-31 21:28 ` Robert Lipe
1999-01-30 11:12 Kaveh R. Ghazi
1999-01-31 23:58 ` Kaveh R. Ghazi
1999-01-30 10:41 Kaveh R. Ghazi
1999-01-30 18:37 ` Jeffrey A Law
1999-01-30 19:58 ` Robert Lipe
1999-01-31 23:58 ` Robert Lipe
1999-01-31 23:58 ` Jeffrey A Law
1999-01-27 14:30 Mike Stump
1999-01-27 15:06 ` Robert Lipe
1999-01-28 10:41 ` Alexandre Oliva
1999-01-28 10:56 ` Jeffrey A Law
1999-01-29 22:20 ` Robert Lipe
1999-01-31 23:58 ` Jeffrey A Law
1999-01-31 23:58 ` Alexandre Oliva
1999-01-31 23:58 ` Robert Lipe
1999-01-31 23:58 ` Mike Stump
1999-01-27 11:33 Mike Stump
1999-01-27 12:52 ` autoconf between stages. was: " Robert Lipe
1999-01-31 23:58 ` Robert Lipe
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=199901300306.DAA08224@phal.cygnus.co.uk \
--to=amylaar@cygnus.co.uk \
--cc=egcs@cygnus.com \
--cc=ghazi@caip.rutgers.edu \
--cc=jbuck@Synopsys.COM \
--cc=law@cygnus.com \
--cc=mrs@wrs.com \
--cc=robertlipe@usa.net \
/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).