public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Alessandro Carminati via Libc-help <libc-help@sourceware.org>
Cc: Alessandro Carminati <alessandro.carminati@gmail.com>
Subject: Re: Fwd: MIPSEL GLIBC sem_init() not shared
Date: Fri, 12 Mar 2021 17:04:17 +0100	[thread overview]
Message-ID: <87im5w4av2.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAPp5cGREJe02DmO5WastxPWEMjZf698usVPatgLpen1H3FTm9A@mail.gmail.com> (Alessandro Carminati via Libc-help's message of "Fri, 12 Mar 2021 14:41:15 +0100")

* Alessandro Carminati via Libc-help:

> Al the sources I have found seems to agree on the fact that if a
> symbol is unversioned, like in my case, the symbol the dynamic linker
> should use is the one that carries the "@@"

I think they talk about the link editor (static linker) chosing the
symbol version, and not about what happens at run time.

> In my scenario, the symbol which carries the double @@ is the
> sem_init@@GLIBC_2_2.
> If the dynamic linker would have picked it, as it should, if I
> correctly interpret what I read, I wouldn't be here asking.

Old binaries originally linked against glibc without symbol versioning
would also use sem_init@@GLIBC_2.2 as the result, but that would result
in breakage because the type sizes are different.

Thanks,
Florian


  reply	other threads:[~2021-03-12 16:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12  9:31 Alessandro Carminati
2021-03-12 10:49 ` Florian Weimer
     [not found]   ` <CAPp5cGTfu38orQNtDRXrxenPDKYbJgEmFHjcw8QspURmCkZL0Q@mail.gmail.com>
2021-03-12 11:37     ` Fwd: " Alessandro Carminati
2021-03-12 12:17       ` Florian Weimer
2021-03-12 13:41         ` Alessandro Carminati
2021-03-12 16:04           ` Florian Weimer [this message]
2021-03-13  6:53             ` Alessandro Carminati
2021-03-13  7:05               ` 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=87im5w4av2.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=alessandro.carminati@gmail.com \
    --cc=libc-help@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).