From: Mark Wielaard <mark@klomp.org>
To: Ulf Hermann <ulf.hermann@qt.io>
Cc: "elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Symbol versioning (Was: [Bug general/24000] couple of testsuite fails with uclibc library)
Date: Tue, 19 Feb 2019 10:48:00 -0000 [thread overview]
Message-ID: <20190219104832.GA9572@wildebeest.org> (raw)
In-Reply-To: <c7f83051-93b6-526c-7bae-a1b2268f63c1@qt.io>
On Tue, Feb 19, 2019 at 07:59:53AM +0000, Ulf Hermann wrote:
> >>> Don't disable symbol versioning, without it binary compatibility is broken.
> >> As per the following commit disabled symbol versioning for uclibc
> >> https://sourceware.org/git/?p=elfutils.git;a=commit;
> >> h=bafacacaf7659a4933604662daba26a480b29a8d
> >>
> >> with uclibc,the test suite hangs in middle when compiled with Symbol
> >> versioning
> >
> > hmmm. I think that commit might have been a mistake in hindsight.
>
> The option to disable symbol versioning is appreciated here. I don't
> think it's a mistake. There are platforms which don't support symbol
> versioning at all.
The problem is that without it every elfutils release would (possibly)
break the ABI between the shared libraries and programs using them.
And we don't have/use a different mechanism to indicate symbols/ABI
changed. How do you prevent things breaking when upgrading the
elfutils libraries?
Cheers,
Mark
next prev parent reply other threads:[~2019-02-19 10:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 14:12 [Bug general/24000] New: couple of testsuite fails with uclibc library ksd.selvakumar at yahoo dot in
2019-01-06 21:06 ` [Bug general/24000] " mark at klomp dot org
2019-01-07 8:30 ` ksd.selvakumar at yahoo dot in
2019-01-13 21:22 ` mark at klomp dot org
2019-01-19 8:31 ` ksd.selvakumar at yahoo dot in
2019-01-23 19:46 ` mark at klomp dot org
2019-02-01 9:31 ` ksd.selvakumar at yahoo dot in
2019-02-01 9:35 ` ksd.selvakumar at yahoo dot in
2019-02-09 21:52 ` mark at klomp dot org
2019-02-09 22:04 ` mark at klomp dot org
2019-02-18 12:09 ` ksd.selvakumar at yahoo dot in
2019-02-18 12:16 ` ksd.selvakumar at yahoo dot in
2019-02-18 18:51 ` mark at klomp dot org
2019-02-18 18:54 ` mark at klomp dot org
2019-02-19 8:00 ` Ulf Hermann
2019-02-19 10:48 ` Mark Wielaard [this message]
2019-02-19 11:30 ` Symbol versioning (Was: [Bug general/24000] couple of testsuite fails with uclibc library) Ulf Hermann
2019-02-19 11:53 ` Mark Wielaard
2019-02-18 21:44 ` [Bug general/24000] couple of testsuite fails with uclibc library mark at klomp dot org
2019-02-19 10:40 ` ksd.selvakumar at yahoo dot in
2019-02-19 15:40 ` [Bug general/24000] couple of ELF compression " mark at klomp dot org
2019-02-20 6:04 ` ksd.selvakumar at yahoo dot in
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=20190219104832.GA9572@wildebeest.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=ulf.hermann@qt.io \
/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).