mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Timo Teras <timo.teras@iki.fi>
To: musl@lists.openwall.com
Cc: dalias@aerifal.cx
Subject: Re: Preparing to release 0.9.12
Date: Thu, 25 Jul 2013 10:44:59 +0300	[thread overview]
Message-ID: <20130725104459.3c29fc34@vostro> (raw)
In-Reply-To: <20130724200221.GA4256@brightrain.aerifal.cx>

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.

Relatedly, commit f389c4984a (make the dynamic linker find its path
file relative to its own location) introduced the armeb, armhf
variants. Fundamentally, these are distribution specific names. I
believe debian has/had armeb (big-endian OABI; being retired), arm
(little-endian OABI; dead port), armel (little-endian EABI), and now
armhf (little-endian EABI with hard-float). But these are by no means
standard. While it is good that LDSO_ARCH gets good default with this
distinguished. It should be allowed to be overridden by distributions.

So basically I'd like to give at configure time:
 DISTRO_ARCH=armel

Which would then make LDSO_ARCH, and SONAME accordingly. And with the
soname version set, we could do proper binary ugprades (even when not
everything is yet rebuilt).

Thanks,
 Timo


  reply	other threads:[~2013-07-25  7:44 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 [this message]
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
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=20130725104459.3c29fc34@vostro \
    --to=timo.teras@iki.fi \
    --cc=dalias@aerifal.cx \
    --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).