From: Alexandre Oliva <aoliva@redhat.com>
To: Gerhard Franke <Gerhard.Franke@mni.fh-giessen.de>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Is -D_XOPEN_SOURCE=500 necessary in gcc/config/sparc/sol2.h?
Date: Tue, 10 Jul 2001 11:45:00 -0000 [thread overview]
Message-ID: <or66d0vd1j.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20010710144506.A20693@saturn.mni.fh-giessen.de>
On Jul 10, 2001, Gerhard Franke <Gerhard.Franke@mni.fh-giessen.de> wrote:
> Can I safely remove the -D_XOPEN_SOURCE=500 or replace it with some
> other less offensive defines?
I'm afraid this would render libstdc++-v3 useless.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2001-07-10 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 5:45 Gerhard Franke
2001-07-10 11:45 ` Alexandre Oliva [this message]
2001-07-11 4:46 ` Gerhard Franke
2001-07-11 9:28 ` Alexandre Oliva
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=or66d0vd1j.fsf@guarana.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=Gerhard.Franke@mni.fh-giessen.de \
--cc=gcc-help@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).