From: Ulrich Drepper <drepper@redhat.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: binutils@sources.redhat.com, black@ieee.org
Subject: Re: [BUG] ld behavior varies for C++ static initializer depending on .a or .o input
Date: Sun, 13 Apr 2003 23:26:00 -0000 [thread overview]
Message-ID: <3E99F1FB.1030008@redhat.com> (raw)
In-Reply-To: <87he92ngiz.fsf@egil.codesourcery.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Zack Weinberg wrote:
> I'd like to point out that while this is true for static (.a)
> libraries, it is not true for shared (.so) libraries -- the linker
> generates DT_NEEDED entries for every shared library on the command
> line, whether or not they satisfy undefined symbols. Personally I
> consider this a bug.
Agreed, I argued like that for years. If somebody wants the DSO
included s/he can use -u to create and artificial dependency.
- --
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+mfH72ijCOnn/RHQRAtHmAKCnq3OcfkKWRnvmmZI9cyTLCzkeGgCfej6g
ZErCJSskzy+8TJD3Ld+CWos=
=9jUv
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-04-13 23:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 3:43 Hal Black
2003-04-11 4:47 ` Alexandre Oliva
2003-04-12 4:01 ` Hal Black
2003-04-12 5:43 ` Alexandre Oliva
2003-04-12 14:24 ` Hal Black
2003-04-12 16:52 ` Ian Lance Taylor
2003-04-12 18:01 ` Hal Black
2003-04-12 20:45 ` Alexandre Oliva
2003-04-13 2:11 ` Hal Black
2003-04-14 18:41 ` Alexandre Oliva
2003-04-13 22:55 ` Ian Lance Taylor
2003-04-13 23:07 ` Zack Weinberg
2003-04-13 23:15 ` Ian Lance Taylor
2003-04-13 23:26 ` Ulrich Drepper [this message]
2003-04-14 5:14 ` Hal Black
2003-04-14 5:30 ` Ian Lance Taylor
2003-04-11 8:16 ` Alan Modra
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=3E99F1FB.1030008@redhat.com \
--to=drepper@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=black@ieee.org \
--cc=zack@codesourcery.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).