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 13:17:11 +0100	[thread overview]
Message-ID: <87sg505zy0.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAPp5cGRtKiBv2nWrDFtWv90OHmodX4WavqzBOhyQGOqCff_Mbg@mail.gmail.com> (Alessandro Carminati via Libc-help's message of "Fri, 12 Mar 2021 12:37:00 +0100")

* Alessandro Carminati via Libc-help:

> This time was the port on MIPSEL, but before this port, I compiled
> successfully (without -lpthread) on two other architectures: ARM32 and
> x64.  Which is the mechanism why in other architecture, the libpthread
> was included and in MIPS it didn't?

32-bit Arm starts at GLIBC_2.4, x86-64 starts at GLIBC_2.2.5.  The old
versions aren't there, so an underlinked library cannot bind against
them.

> My question is, why it resolved the call picking the
> sem_init@GLIBC_2.0 instead of sem_init@@GLIBC_2.2?

glibc originally did not have symbol versioning, so for backwards
compatibility, unversioned binaries need to pick the oldest available
version.  In theory, we could provide better diagnostics.  But we're
working on moving all libpthread symbols in to libc.so.6, so that their
versions are always visible to the link editor (unless you link with
-nostdblib, but then you are on your own anyway).  That's why the
diagnostics do not seem to be particularly useful in the medium term.

Thanks,
Florian


  reply	other threads:[~2021-03-12 12:17 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 [this message]
2021-03-12 13:41         ` Alessandro Carminati
2021-03-12 16:04           ` Florian Weimer
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=87sg505zy0.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).