From: Jeffrey A Law <law@cygnus.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: rth@cygnus.com, egcs@cygnus.com
Subject: Re: egcs-980115 sunos4/hpux9 gengenrtl.c bootstrap failure
Date: Mon, 19 Jan 1998 02:25:00 -0000 [thread overview]
Message-ID: <9877.885110164@hurl.cygnus.com> (raw)
In-Reply-To: <199801180752.CAA04101@caip.rutgers.edu>
In message < 199801180752.CAA04101@caip.rutgers.edu >you write:
> Jeff,
>
> I thought concatenation is ##. We're referring to the #
> operator, which does stringizing, not concatenating.
Opps. You're absolutely correct.
> Anyway, I think rth's patch works, but it dangerously relies on
> the fact that if !defined(__STDC__) then hopefully cpp replaces macros
> even inside double quotes. I already found one platform where this is
> not true, ie Irix4 cc. That compiler (in default mode, ie -xansi) does
> not define __STDC__, but it understands # and does not replace labels in
> double quotes. But Irix4 is very old, six other systems I tested
> (incluiding Irix6) do work with the above patch.
>
> For this reason I would have preferred if this patch was instead
> an autoconf check to detect if the # operator works in cpp. But I can
> live with the above patch in a crunch.
Richard -- can you take care of this.
jeff
next prev parent reply other threads:[~1998-01-19 2:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-19 2:25 Kaveh R. Ghazi
1998-01-19 2:25 ` Jeffrey A Law [this message]
1998-01-20 4:00 ` Richard Henderson
1998-01-21 9:34 ` Branko Cibej
-- strict thread matches above, loose matches on Subject: below --
1998-01-16 1:51 Kaveh R. Ghazi
1998-01-16 2:26 ` Richard Henderson
1998-01-17 22:30 ` Jeffrey A Law
1998-01-19 2:25 ` Manfred Hollstein
1998-01-19 2:25 ` Andreas Schwab
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=9877.885110164@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=ghazi@caip.rutgers.edu \
--cc=rth@cygnus.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).