From: Richard Earnshaw <rearnsha@arm.com>
To: dne@mayonnaise.net (Daniel Néri)
Cc: gdb-patches@sources.redhat.com, Richard.Earnshaw@arm.com
Subject: Re: RDI on OpenBSD
Date: Thu, 04 Apr 2002 03:03:00 -0000 [thread overview]
Message-ID: <200204041103.MAA11981@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Thu, 04 Apr 2002 11:00:31 BST." <200204041000.LAA05934@cam-mail2.cambridge.arm.com>
> > /* A temporary sop to older compilers */
> > -#if defined (__NetBSD__) || defined (unix)
> > +#if defined (__unix__) || defined (unix)
> > # ifndef __unix /* (good for long-term portability?) */
> >
> > This is wrong. NetBSD doesn't define "__unix__" or "unix". Hence the
> > original test.
>
> Ok, forget that. The compiler defines "unix" (and hence, "__unix__"), so
> that isn't a problem.
Hmm, this is getting silly :-)
It turns out that I was more right the first time, than the second.
Some NetBSD platforms (in particular, those that are ELF) do not define
either "unix" or "__unix__". So we really do need that test for
__NetBSD__ there.
R.
next prev parent reply other threads:[~2002-04-04 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 16:51 Daniel Néri
2002-04-04 1:54 ` Richard Earnshaw
2002-04-04 2:00 ` Richard Earnshaw
2002-04-04 3:03 ` Richard Earnshaw [this message]
2002-04-07 14:08 ` Daniel Néri
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=200204041103.MAA11981@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=dne@mayonnaise.net \
--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