From: hjl@lucon.org (H.J. Lu)
To: law@cygnus.com
Cc: drepper@ipd.info.uni-karlsruhe.de, egcs@cygnus.com
Subject: Re: the dynamic linker bug
Date: Fri, 12 Dec 1997 15:46:00 -0000 [thread overview]
Message-ID: <m0xgb1P-0004ecC@ocean.lucon.org> (raw)
In-Reply-To: <19308.881955381@hurl.cygnus.com>
>
>
> In message <m0xgYTT-0004edC@ocean.lucon.org>you write:
> > Ulrich, you need my __register_frame patch to egcs 971207 and gcc
> > 2.8.0. You also need to put those new ones in libc.map. Please
> > check my previous emails.
> Actually, I tend to agree with Kenner that blah_new is a bad name,
> blah_v2 or something else might make more sense long term just in
> case the interface has to change again.
>
blah_v2 is ok with me. BTW, Kenner's patch also fixes egcs 971207.
I have built glibc 2.1 with egcs 971207 plus Kenner's patch and my
__register_frame patch.
--
H.J. Lu (hjl@gnu.org)
next parent reply other threads:[~1997-12-12 15:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19308.881955381@hurl.cygnus.com>
1997-12-12 15:46 ` H.J. Lu [this message]
[not found] <9712121305.AA19929@vlsi1.ultra.nyu.edu>
1997-12-12 14:32 ` Ulrich Drepper
1997-12-12 15:46 ` H.J. Lu
1997-12-12 3:55 Ulrich Drepper
1997-12-12 1:52 ` 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=m0xgb1P-0004ecC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=drepper@ipd.info.uni-karlsruhe.de \
--cc=egcs@cygnus.com \
--cc=law@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).