From: hjl@lucon.org (H.J. Lu)
To: drepper@gnu.ai.mit.edu (Ulrich Drepper)
Cc: libc-linux@gnu.ai.mit.edu (GNU C Library), egcs@cygnus.com
Subject: egcs and glibc 2.1
Date: Mon, 24 Nov 1997 12:21:00 -0000 [thread overview]
Message-ID: <m0xa506-0004ecC@ocean.lucon.org> (raw)
I have managed to compile egcs with the latest glibc 2.1. I have
to patch both glibc 2.1 and egcs to do that. I have sent my
glibc 2.1 patch to the glibc mailing list. Basically I use
an unused field in _IO_FILE to record the vtable offset since
the new _IO_FILE is bigger than the old one. There is some overhead
in glibc. But it seems work fine with iostream in egcs.
--
H.J. Lu (hjl@gnu.org)
next reply other threads:[~1997-11-24 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-24 12:21 H.J. Lu [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-11-10 14:57 H.J. Lu
1997-11-10 16:08 ` 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=m0xa506-0004ecC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=drepper@gnu.ai.mit.edu \
--cc=egcs@cygnus.com \
--cc=libc-linux@gnu.ai.mit.edu \
/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).