From: Florian Weimer <fw@deneb.enyo.de>
To: Ryan Burn <rnickb731@gmail.com>
Cc: Ryan Burn via Libc-help <libc-help@sourceware.org>
Subject: Re: Trouble with portable linking
Date: Thu, 17 Dec 2020 21:55:15 +0100 [thread overview]
Message-ID: <87zh2ccfv0.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <CACqP_wwR2zeXZgtwASAXQ7+HFXz85DeLA8zZH2RGJKGwkiC8vA@mail.gmail.com> (Ryan Burn's message of "Thu, 17 Dec 2020 12:47:44 -0800")
* Ryan Burn:
> On Thu, Dec 17, 2020 at 12:14 PM Florian Weimer <fw@deneb.enyo.de> wrote:
>
>> If you want to be compatible with glibc versions that check the
>> embedded soname in symbol versions (which is not visible in the @
>> syntax), you need to build a stub library that defines the required
>> symbol versions in the right shared object. There is no way to
>> achieve this with .symver directives.
>
> Thanks for the response! Could you elaborate a little more on how I
> can build the stub library?
Here's a script that generates such a stub DSO from an existing full
DSO:
<https://git.centos.org/rpms/compat-glibc/blob/c7/f/SOURCES/dummylib.sh>
It is not completely correct for data symbols; that part needs a bit
of tweaking to get the alignment right. The resulting assembler file
is architecture-specific because the object sizes and symbol versions
are.
> If I understand correctly, newer versions of glibc will resolve a
> versioned symbol even if the embedded soname doesn't match. Is there a
> way to explicitly define the soname so that I can specify it to
> libpthread?
The link editor copies the soname of the shared object that contains a
versioned symbol definition when it generates the versioned symbol
reference. That's why I think you need that stub DSO. It's the only
way I know of that actually works.
next prev parent reply other threads:[~2020-12-17 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 19:57 Ryan Burn
2020-12-17 20:14 ` Florian Weimer
2020-12-17 20:47 ` Ryan Burn
2020-12-17 20:55 ` Florian Weimer [this message]
2020-12-17 21:08 ` Ryan Burn
2020-12-18 7:48 ` Florian Weimer
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=87zh2ccfv0.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=libc-help@sourceware.org \
--cc=rnickb731@gmail.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).