mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: u-uy74@aetey.se
Cc: musl@lists.openwall.com
Subject: Re: Symbol versioning approximation trips on compat symbols
Date: Mon, 28 Jan 2019 07:34:25 +0100	[thread overview]
Message-ID: <87bm41xpce.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20190127093650.GB30123@example.net> (u-uy's message of "Sun, 27 Jan 2019 10:36:50 +0100")

* u-uy:

> On Sat, Jan 26, 2019 at 11:04:24PM -0500, Rich Felker wrote:
>> For what it's worth, compat symbols would have let us remove symbols
>> that shouldn't have been put in musl, such as lchmod (which confuses
>> broken apps which wrongly expect that, if it exists, it should work)
>
> For what my integrator perspective is worth, exposing brokenness instead
> of catering for it is a Good Thing.
>
> Feature detection is one of the typical areas being messed up, in numerous
> softwares.
>
> Thanks musl for exposing the pitfalls and forcing upstreams think better.

As I explained, precisely that is not the case because the main musl
user, Alpine Linux, builds musl with a broken toolchain that is not
properly targeted to musl's features.  I think the official musl
instructions have the same result.

So far, no one has presented a compelling way how to test for symbol
versioning support.

Thanks,
Florian


  reply	other threads:[~2019-01-28  6:34 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 [this message]
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
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=87bm41xpce.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=musl@lists.openwall.com \
    --cc=u-uy74@aetey.se \
    /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).