From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/13667 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: u-uy74@aetey.se Newsgroups: gmane.linux.lib.musl.general Subject: (OT?) Re: [musl] Symbol versioning approximation trips on compat symbols Date: Mon, 28 Jan 2019 14:08:13 +0100 Message-ID: <20190128130813.GC30123@example.net> References: <87r2d5evvi.fsf@oldenburg2.str.redhat.com> <20190124014340.GV23599@brightrain.aerifal.cx> <20190124110931.GU21289@port70.net> <87sgxi718r.fsf@oldenburg2.str.redhat.com> <20190127040424.GA23599@brightrain.aerifal.cx> <20190127093650.GB30123@example.net> <87bm41xpce.fsf@oldenburg2.str.redhat.com> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="43697"; mail-complaints-to="usenet@blaine.gmane.org" Cc: musl@lists.openwall.com To: Florian Weimer Original-X-From: musl-return-13683-gllmg-musl=m.gmane.org@lists.openwall.com Mon Jan 28 14:08:58 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1go6eo-000BFz-BG for gllmg-musl@m.gmane.org; Mon, 28 Jan 2019 14:08:58 +0100 Original-Received: (qmail 19841 invoked by uid 550); 28 Jan 2019 13:08:55 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 19823 invoked from network); 28 Jan 2019 13:08:55 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=x.fripost.org; h= in-reply-to:content-disposition:content-type:content-type :mime-version:references:message-id:subject:subject:from:from :date:date; s=9df9cdc7e101629b5003b587945afa70; t=1548680923; x= 1550495324; bh=dd5Yk78LKxch9Z0DKMXsc0D+XTi8UPt3zvrfMdeGf7w=; b=M srTAhFUPXnZmw1yblaWe6ZzSCpvRTDkFgQcvUWqknIsZV0Ofp2deZ5T2E8fXkK+t +xJlNdGhcfS/DVAmnH+sfamZQGa8WfOXYu56ory4tQnmdaGXV93iPAHvDhDONQ6j KbGh4++9VEHEs7JeIgX7XkQYMdWd9dvshdEQZdROQ5TWQ+DHt4H/UEcSFRRdgEHC RCVXUKyUAnGeZxXHVnB2MKbddHnmt0loK02Wzs6wkD6mTXjaxdG113M23Lx0vgCX jmqOpu5lvJR+B6WLi5Ov5mHGzICGwj/5Na3W4DzK2tlPv7W9qiwPN/VOm6jOeLS0 dPjvqkfvSC/AqV7+rC+/g== X-Virus-Scanned: Debian amavisd-new at fripost.org Content-Disposition: inline In-Reply-To: <87bm41xpce.fsf@oldenburg2.str.redhat.com> Xref: news.gmane.org gmane.linux.lib.musl.general:13667 Archived-At: On Mon, Jan 28, 2019 at 07:34:25AM +0100, Florian Weimer wrote: > * 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. > So far, no one has presented a compelling way how to test for symbol > versioning support. My comment apparently fell out of context. Sorry for that. It was about applications who make undue assumptions (and as a consequence use misdirected tests). Exposing the failures of those assumptions is vital to be able to make it better. 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. IOW it is for the most part not a technical problem but rather a problem of awareness among application developers. Rune