From: Jakub Jelinek <jakub@redhat.com>
To: binutils@sources.redhat.com
Subject: --as-needed handling of shared libraries that fail -Wl,-z,defs
Date: Thu, 19 May 2005 16:43:00 -0000 [thread overview]
Message-ID: <20050519163716.GD22344@sunsite.mff.cuni.cz> (raw)
Hi!
--as-needed doesn't seem to try satisfy undefined references in shared
libraries:
ldd -d -r /usr/lib64/libreadline.so.4
undefined symbol: BC (/usr/lib64/libreadline.so.4)
undefined symbol: PC (/usr/lib64/libreadline.so.4)
undefined symbol: UP (/usr/lib64/libreadline.so.4)
undefined symbol: tgetnum (/usr/lib64/libreadline.so.4)
undefined symbol: tgoto (/usr/lib64/libreadline.so.4)
undefined symbol: tgetflag (/usr/lib64/libreadline.so.4)
undefined symbol: tputs (/usr/lib64/libreadline.so.4)
undefined symbol: tgetent (/usr/lib64/libreadline.so.4)
undefined symbol: tgetstr (/usr/lib64/libreadline.so.4)
libc.so.6 => /lib64/libc.so.6 (0x0000003a33900000)
/lib64/ld-linux-x86-64.so.2 (0x0000555555555000)
echo 'int main (void) { return 0; }' | gcc -xc - -o test -lreadline -Wl,--as-needed -ltermcap -Wl,--no-as-needed; ./test
./test: symbol lookup error: /usr/lib64/libreadline.so.4: undefined symbol: BC
Is this desirable or should we change --as-needed to attempt to satisfy even
those? Particularly for -lreadline, it makes sense to not depend on
libtermcap resp. libncurses, as those symbols can be provided by either
of those libraries and some applications prefer one over the other and vice
versa.
Jakub
next reply other threads:[~2005-05-19 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 16:43 Jakub Jelinek [this message]
2005-05-20 10:02 ` Alan Modra
2005-05-20 11:31 ` Jakub Jelinek
2005-05-20 13:52 ` Alan Modra
2005-05-20 19:02 ` Mike Hearn
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=20050519163716.GD22344@sunsite.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=binutils@sources.redhat.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).