From: hjl@lucon.org (H.J. Lu)
To: drepper@cygnus.com
Cc: libc-hacker@sourceware.cygnus.com
Subject: Re: The old libio patch for glibc 2.2
Date: Mon, 16 Aug 1999 06:57:00 -0000 [thread overview]
Message-ID: <19990816135641.A16F78EEE@ocean.lucon.org> (raw)
In-Reply-To: <m3yafcv7vs.fsf@localhost.localnet>
>
> hjl@varesearch.com (H.J. Lu) writes:
>
> > The libio change in glibc 2.2 screwed up the binaries compiled against
> > glibc 2.0. This patch seems to work ok. But I don't know if it is the
> > best fix nor if it fixes all the old libio problems.
>
> I would prefer to use versioning buf the duplication of the cost is
> too expensive so I went with your patches.
>
> > Also I am not sure if we should use versioning for _IO_setbuffer and
> > _IO_setvbuf.
>
> I don't think so.
>
Shouldn't that be more consistent? You used versioning on some
functions, oldiofsetpos64.c, oldiofsetpos.c, oldiofgetpos64.c,
and oldiofgetpos.c, for the libio change.
H.J.
next prev parent reply other threads:[~1999-08-16 6:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-10 17:50 H.J. Lu
1999-08-15 18:23 ` Ulrich Drepper
1999-08-16 6:57 ` H.J. Lu [this message]
1999-08-16 9:01 ` Ulrich Drepper
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=19990816135641.A16F78EEE@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=drepper@cygnus.com \
--cc=libc-hacker@sourceware.cygnus.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).