From: Florian Weimer <fw@deneb.enyo.de>
To: Ariadne Conill <ariadne@dereferenced.org>
Cc: musl@lists.openwall.com
Subject: Re: [musl] friendly errors for ABI mismatch
Date: Mon, 27 Jul 2020 23:16:56 +0200 [thread overview]
Message-ID: <87mu3kd5fb.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <1667998.jfqktxE8f0@localhost> (Ariadne Conill's message of "Mon, 27 Jul 2020 09:27:28 -0600")
* Ariadne Conill:
> On 32-bit systems, musl 1.2 has a new ABI (due to time64). This
> results in programs built against musl 1.2 failing to run against
> musl 1.1. That part is fine, but you get an error message about
> being unable to relocate symbols, which is not really insightful if
> you don't know about the ABI break.
Are you concerned about static linking across musl versions, or the
dynamic run-time behavior?
There are limits what you can do without changing the entire
toolchain.
> glibc, on the other hand, has a minimum version specified in every
> binary, and prints an error message saying the glibc is too old if
> this situation is encountered.
Do you mean symbol versioning? It's a bit more flexible than that.
Symbol versions are only required if a symbol with that version is
actually used. And the symbol version does not have to be a number or
(in the GNU implementation) imply some sort of linear order.
Using symbol versioning has the advantage that the rest of the
toolchain already supports it.
prev parent reply other threads:[~2020-07-27 21:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 15:27 Ariadne Conill
2020-07-27 16:03 ` Rich Felker
2020-07-27 20:54 ` A. Wilcox
2020-07-27 20:57 ` Ariadne Conill
2020-07-27 21:50 ` Rich Felker
2020-07-28 8:40 ` Florian Weimer
2020-07-29 1:16 ` Rich Felker
2020-07-27 21:16 ` Florian Weimer [this message]
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=87mu3kd5fb.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=ariadne@dereferenced.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).