From: Jeffrey A Law <law@cygnus.com>
To: hjl@lucon.org (H.J. Lu)
Cc: egcs@cygnus.com, drepper@gnu.ai.mit.edu (Ulrich Drepper)
Subject: Re: An egcs patch for libio
Date: Fri, 05 Dec 1997 23:33:00 -0000 [thread overview]
Message-ID: <26837.881393807@hurl.cygnus.com> (raw)
In-Reply-To: <m0xdJwR-0004ecC@ocean.lucon.org>
In message < m0xdJwR-0004ecC@ocean.lucon.org >you write:
> This patch is needed for glibc 2. BTW, libio in egcs is not compatible
> with libio in glibc 2.1. I have patches for both glibc 2.1 and egcs.
> But they have to go tegether.
>
> FYI, the _lock field in _IO_stdin/_IO_stdout/_IO_stderr is not
> newed. It is a static variable.
>
> --
> H.J. Lu (hjl@gnu.org)
> ----
> Wed Dec 3 10:49:39 1997 H.J. Lu (hjl@gnu.org)
>
> * streambuf.cc (streambuf::~streambuf): Don't delete _lock
> for _IO_stdin/_IO_stdout/_IO_stderr.
Thanks. I've installed this patch.
jeff
next prev parent reply other threads:[~1997-12-05 23:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-03 12:54 H.J. Lu
1997-12-05 23:33 ` Jeffrey A Law [this message]
[not found] <87vhx5aigr.fsf@mharnois.workgroup.net>
1997-12-04 13:27 ` H.J. Lu
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=26837.881393807@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=drepper@gnu.ai.mit.edu \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.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).