From: Ulrich Drepper <drepper@ipd.info.uni-karlsruhe.de>
To: Neal Becker <neal@ctd.comsat.com>
Cc: hjl@lucon.org (H.J. Lu),
egcs@cygnus.com, libc-linux@gnu.org (GNU C Library)
Subject: Re: A glibc or egcs bug?
Date: Sun, 07 Dec 1997 09:34:00 -0000 [thread overview]
Message-ID: <x7afedcb5f.fsf@myware.rz.uni-karlsruhe.de> (raw)
In-Reply-To: <u9n2iddrd4.fsf@neal.ctd.comsat.com>
Neal Becker <neal@ctd.comsat.com> writes:
> The related question is, why are we hitting this union wait stuff at
> all, if we don't ask for -D_BSD? I thought glibc would favor POSIX in
> cases of conflict. Using the old BSD union wait is hardly ever
> needed.
We have the feature of the transparent unions, so why not use it. It
is much cleaner than requiring defines.
-- Uli
---------------. drepper at gnu.org ,-. Rubensstrasse 5
Ulrich Drepper \ ,-------------------' \ 76149 Karlsruhe/Germany
Cygnus Solutions `--' drepper at cygnus.com `------------------------
next prev parent reply other threads:[~1997-12-07 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-06 19:21 H.J. Lu
1997-12-06 20:21 ` Ulrich Drepper
1997-12-06 23:47 ` H.J. Lu
1997-12-07 8:56 ` Neal Becker
1997-12-07 9:34 ` Ulrich Drepper [this message]
1997-12-07 13:04 ` Roland McGrath
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=x7afedcb5f.fsf@myware.rz.uni-karlsruhe.de \
--to=drepper@ipd.info.uni-karlsruhe.de \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.org \
--cc=libc-linux@gnu.org \
--cc=neal@ctd.comsat.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).