From: Ulrich Drepper <drepper@cygnus.com>
To: Ian Lance Taylor <ian@zembu.com>
Cc: law@cygnus.com, binutils@sourceware.cygnus.com
Subject: Re: Dealing with broken ELF libraries
Date: Thu, 02 Sep 1999 09:09:00 -0000 [thread overview]
Message-ID: <m3btblmh6u.fsf@localhost.localnet> (raw)
In-Reply-To: <19990902135728.8531.qmail@daffy.airs.com>
Ian Lance Taylor <ian@zembu.com> writes:
> I don't know if HP tried anything similar.
Probably not. It's only MIPS where the difference between static and
dynamic binaries is so huge due to the mis-design of the lazy
relocation. Beside, HP has acquired from Sun the NSS technology which
on traditional dynamic loading systems prohibits static linking.
(Only exception: glibc).
--
---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com `------------------------
next prev parent reply other threads:[~1999-09-02 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-01 15:47 Jeffrey A Law
1999-09-01 16:03 ` Ulrich Drepper
1999-09-01 16:11 ` Jeffrey A Law
1999-09-02 6:57 ` Ian Lance Taylor
1999-09-02 9:09 ` Ulrich Drepper [this message]
1999-09-02 6:55 ` Ian Lance Taylor
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=m3btblmh6u.fsf@localhost.localnet \
--to=drepper@cygnus.com \
--cc=binutils@sourceware.cygnus.com \
--cc=ian@zembu.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).