From: Yann Droneaud <ydroneaud@opteya.com>
To: libc-alpha@sourceware.org
Subject: Compatibility .so linker scripts for merged libraries
Date: Tue, 16 Nov 2021 14:27:05 +0100 [thread overview]
Message-ID: <4f1e47f0-e9ae-a2ce-7c12-bd8d4d6adba5@opteya.com> (raw)
Hi,
Was it considered dangerous to introduce "compatibility" .so link
scripts for the libraries that was merged into libc.so (libpthread,
librt, libdl, etc.) ?
For example:
$ cat librt.so
/* GNU ld script
Use the static library */
OUTPUT_FORMAT(elf64-x86-64)
GROUP ( /lib/x86_64-linux-gnu/librt.a )
Because I'm having some bad times fixing issues in a build system that
try to locate now missing .so with gcc -print-file-name= then uses the
paths to the libraries instead of -l name them.
Regards.
--
Yann Droneaud
OPTEYA
next reply other threads:[~2021-11-16 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 13:27 Yann Droneaud [this message]
2021-11-16 13:47 ` Andreas Schwab
2021-11-16 13:54 ` Yann Droneaud
2021-11-17 10:31 ` Florian Weimer
2021-11-17 21:32 ` Yann Droneaud
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=4f1e47f0-e9ae-a2ce-7c12-bd8d4d6adba5@opteya.com \
--to=ydroneaud@opteya.com \
--cc=libc-alpha@sourceware.org \
/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).