mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Markus Wichmann <nullplan@gmx.net>
To: musl@lists.openwall.com
Subject: Re: (OT?) Re: [musl] Symbol versioning approximation trips on compat symbols
Date: Mon, 28 Jan 2019 16:22:45 +0100	[thread overview]
Message-ID: <20190128152244.GA28581@voyager> (raw)
In-Reply-To: <20190128130813.GC30123@example.net>

On Mon, Jan 28, 2019 at 02:08:13PM +0100, u-uy74@aetey.se wrote:
> If there is a feature which is hard or impossible to test for, like
> symbol versioning, it means that the applications may _have_ to rely on
> an explicit build flag telling whether to use it.
> 

Why is symbol versioning hard to test for, again? You make a library
containing two versions of the same function, one returns one, the other
two. The one that returns one is the default symbol. The test
application tries to link against the version that returns two. If that
works, symbol versioning is supported.

Or do you have to take care of toolchains without shared linking support
as well? Is there such a thing as static libs with symbol versioning?

Ciao,
Markus


  reply	other threads:[~2019-01-28 15:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21 17:57 Florian Weimer
2019-01-24  1:43 ` Rich Felker
2019-01-24  9:28   ` u-uy74
2019-01-24 10:11     ` Florian Weimer
2019-01-24 11:09   ` Szabolcs Nagy
2019-01-24 11:18     ` Florian Weimer
2019-01-27  4:04       ` Rich Felker
2019-01-27  9:36         ` u-uy74
2019-01-28  6:34           ` Florian Weimer
2019-01-28  9:17             ` Timo Teras
2019-01-28 11:33               ` Szabolcs Nagy
2019-01-28 12:40             ` Szabolcs Nagy
2019-01-28 13:08             ` (OT?) Re: [musl] " u-uy74
2019-01-28 15:22               ` Markus Wichmann [this message]
2019-01-28 15:34                 ` Rich Felker
2019-01-28 15:29               ` Rich Felker
2019-01-29 17:13                 ` u-uy74
2019-01-30 14:57                   ` Rich Felker
2019-01-28 21:57             ` A. Wilcox
2019-01-28 22:52               ` Matias Fonzo
2019-01-28 23:12                 ` Zach van Rijn
2019-01-28 23:41                   ` A. Wilcox
2019-01-28 23:47                     ` Rich Felker
2019-01-29  3:22                       ` A. Wilcox
2019-01-29 19:40                         ` Matias Fonzo
2019-01-29 19:31                   ` Matias Fonzo

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=20190128152244.GA28581@voyager \
    --to=nullplan@gmx.net \
    --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).