From: tb@MIT.EDU (Thomas Bushnell, n/BSG)
To: drepper@cygnus.com
Cc: schwab@issan.informatik.uni-dortmund.de, libc-hacker@cygnus.com,
ian@cygnus.com, gas2@cygnus.com, libc-hacker@gnu.org
Subject: Re: An ELF linker patch
Date: Mon, 04 May 1998 15:53:00 -0000 [thread overview]
Message-ID: <199805042253.SAA20231@steve-dallas.MIT.EDU> (raw)
In-Reply-To: <r2iunmggbb.fsf@happy.cygnus.com>
From: Ulrich Drepper <drepper@cygnus.com>
Date: 04 May 1998 09:18:48 -0700
IMO we shouldn't present the mxing of dynamic and static binaries as a
usable way. Everybody should use dynamic binaries, only in very
special cases it might be desirable to rely on this feature.
I agree, but I think this means it should be a priority to have a
static-only version of NSS.
next prev parent reply other threads:[~1998-05-04 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-30 11:54 H.J. Lu
1998-04-30 12:07 ` Ian Lance Taylor
1998-05-04 1:51 ` Andreas Schwab
1998-05-04 9:21 ` Ulrich Drepper
1998-05-04 15:53 ` Thomas Bushnell, n/BSG [this message]
1998-05-04 16:37 ` 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=199805042253.SAA20231@steve-dallas.MIT.EDU \
--to=tb@mit.edu \
--cc=drepper@cygnus.com \
--cc=gas2@cygnus.com \
--cc=ian@cygnus.com \
--cc=libc-hacker@cygnus.com \
--cc=libc-hacker@gnu.org \
--cc=schwab@issan.informatik.uni-dortmund.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).