From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Adjustments to roadmap
Date: Sun, 30 Aug 2015 11:00:13 +0200 [thread overview]
Message-ID: <20150830090009.GH3609@port70.net> (raw)
In-Reply-To: <20150830053037.GK7833@brightrain.aerifal.cx>
* Rich Felker <dalias@libc.org> [2015-08-30 01:30:37 -0400]:
> On Sun, Aug 30, 2015 at 12:13:53PM +0700, ???????? wrote:
> > I also do not use
> > recent gcc, so I don't know which problems have arised again and why
> > now again "libgcc_s breaks" (and why I don't even have it in my
> > systems, both "desktop" and "server" configurations which include C++
> > complex code like qt4).
>
> This is not an option for everyone. For example your version of gcc
> does not have aarch64 support, nor does it have risc-v support which
> is not even in upstream gcc yet afaik, and which will be very
> important for future open hardware that free and auditable all the way
the libgcc_s issue is x86 specific (because only x86 had the
broken ifunc based multiversioning support)
it is possible to patch out, but would make it impossible to
use musl-gcc wrapper with existing gcc-6.* on x86
there are other reasons for symvers: debian is willing to
accept patches for a musl based debian, however they use
symbol versioning a lot to avoid frequently changing the .so
name. i.e. if we support symvers we may be able to create
a musl based debian package repo without much effort or
maintainance work. (it is probably possible to rebuild all
dependent packages on every minor abi change in a library,
but then somebody would need to do that work and users will
need to download more packages on an update).
next prev parent reply other threads:[~2015-08-30 9:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 2:43 Rich Felker
2015-08-28 3:38 ` Khem Raj
2015-08-28 4:21 ` Rich Felker
2015-08-28 6:57 ` Вася Бойцов
2015-08-28 12:47 ` Rich Felker
2015-08-28 12:16 ` Justin Cormack
2015-08-28 7:24 ` u-wsnj
2015-08-28 11:39 ` Рысь
2015-08-28 17:18 ` Rich Felker
2015-08-30 4:21 ` Рысь
2015-08-30 4:46 ` Rich Felker
2015-08-30 5:13 ` Рысь
2015-08-30 5:30 ` Rich Felker
2015-08-30 9:00 ` Szabolcs Nagy [this message]
2015-08-30 17:09 ` Rich Felker
2015-08-30 17:45 ` u-wsnj
2015-08-30 17:13 ` Рысь
2015-08-30 17:38 ` Rich Felker
2015-08-30 5:18 ` Рысь
2015-08-30 5:31 ` Rich Felker
2015-08-30 17:21 ` Рысь
2015-08-30 19:29 ` Message localization [Was: Re: [musl] Adjustments to roadmap] Rich Felker
2015-09-01 4:26 ` Рысь
2015-09-01 4:47 ` Rich Felker
2015-09-02 2:26 ` Рысь
2015-09-02 2:28 ` Rich Felker
2015-09-07 13:51 ` Рысь
2015-09-08 15:18 ` Rich Felker
2015-08-31 7:09 ` Adjustments to roadmap 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=20150830090009.GH3609@port70.net \
--to=nsz@port70.net \
--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).