From: Andreas Jaeger <aj@suse.de>
To: Ralf Baechle <ralf@uni-koblenz.de>
Cc: GNU libc hacker <libc-hacker@sourceware.cygnus.com>
Subject: Re: Multiple definition of __libc_multiple_libcs
Date: Mon, 24 Jan 2000 23:46:00 -0000 [thread overview]
Message-ID: <u8ogaasjpf.fsf@gromit.rhein-neckar.de> (raw)
In-Reply-To: <20000124160352.B16426@uni-koblenz.de>
>>>>> Ralf Baechle writes:
[...]
Ralf> Is this vanilla 2.9.5 or the one from oss.sgi.com with my patches applied?
One with your patches applied.
Ralf> I remember having fixed various bugs like this but it's too long since then,
Ralf> forgot all the details.
Here's the ChangeLog entry for the patch - it's fixed in current glibc
2.2 CVS.
Andreas
2000-01-11 Andreas Schwab <schwab@suse.de>
* sysdeps/mips/__longjmp.c (__longjmp): Change call to abort into
infinite loop to avoid pulling in stdio in the dynamic linker.
* sysdeps/mips/mips64/__longjmp.c (__longjmp): Likewise.
-
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.rhein-neckar.de
prev parent reply other threads:[~2000-01-24 23:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-10 8:35 Andreas Jaeger
2000-01-10 9:09 ` Andreas Schwab
2000-01-24 14:46 ` Ralf Baechle
2000-01-24 23:46 ` Andreas Jaeger [this message]
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=u8ogaasjpf.fsf@gromit.rhein-neckar.de \
--to=aj@suse.de \
--cc=libc-hacker@sourceware.cygnus.com \
--cc=ralf@uni-koblenz.de \
/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).