From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/3750 Path: news.gmane.org!not-for-mail From: Isaac Newsgroups: gmane.linux.lib.musl.general Subject: Re: Preparing to release 0.9.12 Date: Thu, 25 Jul 2013 17:38:51 -0700 Message-ID: <20130726003851.GA20873@newbook> References: <20130724200221.GA4256@brightrain.aerifal.cx> <20130725104459.3c29fc34@vostro> <20130725161654.GH4284@brightrain.aerifal.cx> <20130725195955.25cbc101@vostro> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1374799147 28576 80.91.229.3 (26 Jul 2013 00:39:07 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 26 Jul 2013 00:39:07 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-3754-gllmg-musl=m.gmane.org@lists.openwall.com Fri Jul 26 02:39:10 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1V2W3p-0002Cm-MN for gllmg-musl@plane.gmane.org; Fri, 26 Jul 2013 02:39:09 +0200 Original-Received: (qmail 14109 invoked by uid 550); 26 Jul 2013 00:39:07 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 14096 invoked from network); 26 Jul 2013 00:39:06 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=lavabit; d=lavabit.com; b=oNxPYW1IFlFVtSdPlXIxVxmYS8YsvV5OgR7kTiH6zQcUX8EBPa4eSELT80hgqsnLLCT7GCLAqWJXCnStsIAACs71LF74aLl795WclnTb1I+IFmdntxqSUPQ24Rdqxy+dj0/GcRdcZceoIgcvkyPMqS5UAjtN0cMGUKZmKHYFtCY=; h=Date:From:To:Subject:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:User-Agent; Content-Disposition: inline In-Reply-To: <20130725195955.25cbc101@vostro> User-Agent: Mutt/1.5.20 (2009-06-14) Xref: news.gmane.org gmane.linux.lib.musl.general:3750 Archived-At: On Thu, Jul 25, 2013 at 07:59:55PM +0300, Timo Teras wrote: > On Thu, 25 Jul 2013 12:16:55 -0400 > Rich Felker wrote: > > > On Thu, Jul 25, 2013 at 10:44:59AM +0300, Timo Teras wrote: > > > On Wed, 24 Jul 2013 16:02:21 -0400 > > > Rich Felker wrote: > > > > > > > The list of changes since 0.9.11 has grown quite large, and > > > > although we haven't met some of the roadmap goals for 0.9.12, > > > > others that were marked for 0.9.13 have already been finished. So > > > > I think it's reasonable to aim to release very soon now. There > > > > are still a few pending items I'd like to get committed before > > > > the release: > > > > > > > > - orc's getaddrinfo fix for AF_UNSPEC with NULL hostname > > > > - Andre's ARM memcpy optimizations > > > > - New crt1.c code for adding PIE support for more archs > > > > - MAYBE the symlink direction issue... > > > > > > Since the C++ ABI was fixed, it means that any current native musl > > > toolchain will get C++ ABI breakage? > > > > > > In this case the symlink direction issue would help with smoother > > > transitions. It would be also crucial to start using proper SONAME > > > versioning, so we could handle binary upgrades smoothly. > > > > This would not help. The ABI between the application and musl's > > libc.so has not changed since just after the initial public release, > > except for some bugs that had arch-specific structures laid out wrong, > > etc. -- and in this case, programs built before the fix were not > > working at all anyway when using the affected feature. > > The so versioning will not help for C++ related things. The most > important use case I had in mind is that, package managers that use > soversions for automatic dependencies, can insert proper "require > version XXX or later of this .so". That is, if we built with musl X, we > can detect that from .so, and record it. And later ensure that musl X-1 > will not satisfy the newly built package's dependencies. Especially > important when we are introducing new symbols. On Debian, there's the "symbols" system; this lists all symbols with the version they appeared in, and the tools look through the symbols and find the lowest version providing all the symbols. But as a standard rule, _added_ symbols _do_ _not_ call for a new SONAME, since they do not break the ABI. -- Isaac Dunham