From: Andrew Haley <aph@redhat.com>
To: tromey@redhat.com
Cc: GCC Hackers <gcc@gcc.gnu.org>
Subject: Re: gcc-3.2 build problem in the java area
Date: Fri, 11 Oct 2002 10:35:00 -0000 [thread overview]
Message-ID: <15783.1013.475511.998095@cuddles.cambridge.redhat.com> (raw)
In-Reply-To: <877kgpgd1y.fsf@fleche.redhat.com>
Tom Tromey writes:
> >>>>> "Russ" == Russ Allbery <rra@stanford.edu> writes:
>
> Russ> Solaris only defines MAXHOSTNAMELEN if:
> Russ> #if !defined(_XPG4_2) || defined(__EXTENSIONS__)
>
> Is there any drawback to simply always defining __EXTENSIONS__?
> We could do that in include/posix.h.
But who might know what else __EXTENSIONS__ might do? I suppose we
could "#ifdef __solaris" or somesuch.
It might be lees risky to "#ifdef __solaris .. #define MAXHOSTNAMELEN 256
Andrew.
next prev parent reply other threads:[~2002-10-11 17:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 10:07 cyan
2002-10-10 10:21 ` Andrew Haley
2002-10-10 10:25 ` cyan
2002-10-11 2:32 ` Russ Allbery
2002-10-11 10:20 ` Tom Tromey
2002-10-11 10:35 ` Andrew Haley [this message]
2002-10-11 10:55 ` David Edelsohn
2002-10-11 11:41 ` Tom Tromey
2002-10-11 11:49 ` Andrew Haley
2002-10-11 11:49 ` Tom Tromey
2002-10-11 12:08 ` Andrew Haley
2002-10-12 10:03 ` Kaveh R. Ghazi
2002-10-11 13:57 ` Jeff Sturm
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=15783.1013.475511.998095@cuddles.cambridge.redhat.com \
--to=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).