From: Isaac <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: Preparing to release 0.9.12
Date: Thu, 25 Jul 2013 17:38:51 -0700 [thread overview]
Message-ID: <20130726003851.GA20873@newbook> (raw)
In-Reply-To: <20130725195955.25cbc101@vostro>
On Thu, Jul 25, 2013 at 07:59:55PM +0300, Timo Teras wrote:
> On Thu, 25 Jul 2013 12:16:55 -0400
> Rich Felker <dalias@aerifal.cx> 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 <dalias@aerifal.cx> 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
next prev parent reply other threads:[~2013-07-26 0:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 20:02 Rich Felker
2013-07-25 7:44 ` Timo Teras
2013-07-25 15:05 ` Szabolcs Nagy
2013-07-25 15:45 ` Timo Teras
2013-07-25 16:39 ` Rich Felker
2013-07-25 16:16 ` Rich Felker
2013-07-25 16:59 ` Timo Teras
2013-07-25 17:18 ` Rich Felker
2013-07-25 17:27 ` Rich Felker
2013-07-26 0:38 ` Isaac [this message]
2013-07-26 2:08 ` Rich Felker
2013-07-26 5:13 ` Timo Teras
2013-07-26 5:34 ` Rich Felker
2013-07-26 6:07 ` Timo Teras
2013-07-26 6:18 ` Rich Felker
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=20130726003851.GA20873@newbook \
--to=idunham@lavabit.com \
--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).