From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/5410 Path: news.gmane.org!not-for-mail From: Carlos Breviglieri Newsgroups: gmane.linux.lib.musl.general Subject: Re: Aboriginal musl support Date: Fri, 4 Jul 2014 09:33:36 -0300 Message-ID: References: <20140703205039.GB179@brightrain.aerifal.cx> <53B5F1D7.4000402@skarnet.org> <1404441610.1648.0.camel@gandalf.lan.sholland.net> <20140704032546.GD179@brightrain.aerifal.cx> <20140706061827.GA2587@newbook> <20140704054612.GF179@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c2e9309c0e5c04fd5d55b4 X-Trace: ger.gmane.org 1404477244 10919 80.91.229.3 (4 Jul 2014 12:34:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 4 Jul 2014 12:34:04 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-5415-gllmg-musl=m.gmane.org@lists.openwall.com Fri Jul 04 14:33:54 2014 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 1X32gZ-0001hN-Jm for gllmg-musl@plane.gmane.org; Fri, 04 Jul 2014 14:33:51 +0200 Original-Received: (qmail 32760 invoked by uid 550); 4 Jul 2014 12:33:49 -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 32752 invoked from network); 4 Jul 2014 12:33:48 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=educywqyiDQnHPrnLSH1VYH5Ot2siUXiCDwBSGljmBI=; b=Z+KG3/WEnBG11d6hxc9wUwF6hcLMujgQqOM/1aIjnLxXquSB3fjXth7FyGqa9M1EWd IKk3JSInQMR36cmUUSc0VbROHx6j9CW+VGXeDg0KXptCtxMwoXAsGSLDFrkPjhTyXInZ aZGKx3gyEzLGYhVsmVpVhY1c7V+LXxkc5+wtisKjnyW4fN/GKImAAbh4qM6tngMqjc5s YmSZG+IDPL8DX0jiTbodO3it1myXR2QwyJqqGoTuS9tCInJTWk82HPXe2B0sGU+1zb8k VI/9+F9xXpn+gqC6tB45QRKyUNIkZ+RLL50n3VSG4/aPwzkHoSjVaVGmXdcNPVqE1naq lo2A== X-Received: by 10.182.236.193 with SMTP id uw1mr12349946obc.12.1404477216917; Fri, 04 Jul 2014 05:33:36 -0700 (PDT) In-Reply-To: <20140704054612.GF179@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:5410 Archived-At: --001a11c2e9309c0e5c04fd5d55b4 Content-Type: text/plain; charset=UTF-8 Hey, sorry for the late reply... I saw the announcement at the aboriginal mailing list and confused it with musl's. The link is already posted, but, for reference here it goes. You can check out the commits for details at http://landley.net/hg/aboriginal/rss-log and http://landley.net/notes.html """""" Subject: [Aboriginal] basic musl support is in. To enable it for a given target, comment out the UCLIBC_CONFIG stanza in the sources/targets/$ARCH file. All I can really say at the moment is that it compiles for i686. (That's the ccwrap rewrite, basic script tweaks, and a patch to gcc to not use a nonstandard type name.) Sorry that took so long. It was a lot of debugging. (And now to test build more stuff...) Rob """""" Regards, Carlos On Fri, Jul 4, 2014 at 2:46 AM, Rich Felker wrote: > On Sat, Jul 05, 2014 at 11:18:29PM -0700, Isaac Dunham wrote: > > On Thu, Jul 03, 2014 at 11:25:46PM -0400, Rich Felker wrote: > > > On Thu, Jul 03, 2014 at 09:40:10PM -0500, Samuel Holland wrote: > > > > On Fri, 2014-07-04 at 01:14 +0100, Laurent Bercot wrote: > > > > > On 03/07/2014 22:22, Carlos Breviglieri wrote: > > > > > > I also keep an eye on aboriginal linux for other architectures > testings, > > > > > > which, just now, announced basic musl compatibility... sweet. > > > > > > > > > > Where did you see that announcement ? I can see nothing on > landley.net. > > > > > I've been waiting for the Aboriginal native musl toolchains for a > while > > > > > and chafing at the bit. It would be sweet if they were finally > ready. > > > > > (Rob, can you confirm/deny ?) > > > > > > > > > > > > > > http://lists.landley.net/pipermail/aboriginal-landley.net/2014-July/001399.html > > > > > > Has anyone had a chance to look at this yet? It would be nice if > > > someone with experience with distros/building could help check for > > > common breakage/pitfalls. I know Aboriginal is using a much older > > > toolchain than most musl users, so that might also have some new > > > > Similar version (4.2.1) to bootstrap-linux (4.2.2?), also the oldest > > supported by musl-cross; I used GCC 3.4 and 4.2.1 with some patches > > for the latter from both musl-cross and Aboriginal. > > OK good to know. > > > > issues that others haven't encountered. I suspect there might still be > > > issues with libgcc.a symbol visibility that would result in broken > > > binaries when dynamic linking against musl; this should be easy to > > > check. > > > > See the threads of Jan 11/12. > > (Rob could not duplicate.) > > Yes, that's why I suspect the bug may still be present: he was only > concerned with finding a test case showing it breaking something and > was not convinced merely by the presence of the visible symbols that > break the ABI. > > This is part of why I think it may be beneficial to work around broken > libgcc.a on musl's side: the breakage is subtle when it happens and > it's hard to convince users that there really is a bug. > > Rich > --001a11c2e9309c0e5c04fd5d55b4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hey, sorry for the late reply... I saw the announceme= nt at the aboriginal mailing list and confused it with musl's. The link= is already posted, but, for reference here it goes. You can check out the = commits for details at http://landley.net/hg/aboriginal/rss-log and http://landley.net/notes.html

""""""
Subject: [Aboriginal] basic musl support is in.

To enable it for a given target, comment out the UCLIBC_CONFIG stanza in the sources/targets/$ARCH file.

All I can really say at the moment is that it compiles for i686. (That'= s
the ccwrap rewrite, basic script tweaks, and a patch to gcc to not use a nonstandard type name.)

Sorry that took so long. It was a lot of debugging. (And now to test
build more stuff...)

Rob
""""""

Regards,

Ca= rlos


On Fri, Jul 4, 2014 at 2:46 AM, Rich Felker <dalias@libc.org> wrote:
On Sat, Jul 05, 2014 at 11:1= 8:29PM -0700, Isaac Dunham wrote:
> On Thu, Jul 03, 2014 at 11:25:46PM -0400, Rich Felker wrote:
> > On Thu, Jul 03, 2014 at 09:40:10PM -0500, Samuel Holland wrote: > > > On Fri, 2014-07-04 at 01:14 +0100, Laurent Bercot wrote:
> > > > On 03/07/2014 22:22, Carlos Breviglieri wrote:
> > > > > I also keep an eye on aboriginal linux for other a= rchitectures testings,
> > > > > which, just now, announced basic musl compatibilit= y... sweet.
> > > >
> > > > =C2=A0 Where did you see that announcement ? I can see = nothing on landley.net= .
> > > > I've been waiting for the Aboriginal native musl to= olchains for a while
> > > > and chafing at the bit. It would be sweet if they were = finally ready.
> > > > (Rob, can you confirm/deny ?)
> > > >
> > >
> > > http://lists.landley.net/= pipermail/aboriginal-landley.net/2014-July/001399.html
> >
> > Has anyone had a chance to look at this yet? It would be nice if<= br> > > someone with experience with distros/building could help check fo= r
> > common breakage/pitfalls. I know Aboriginal is using a much older=
> > toolchain than most musl users, so that might also have some new<= br> >
> Similar version (4.2.1) to bootstrap-linux (4.2.2?), also the oldest > supported by musl-cross; I used GCC 3.4 and 4.2.1 with some patches > for the latter from both musl-cross and Aboriginal.

OK good to know.

> > issues that others haven't encountered. I suspect there might= still be
> > issues with libgcc.a symbol visibility that would result in broke= n
> > binaries when dynamic linking against musl; this should be easy t= o
> > check.
>
> See the threads of Jan 11/12.
> (Rob could not duplicate.)

Yes, that's why I suspect the bug may still be present: he was on= ly
concerned with finding a test case showing it breaking something and
was not convinced merely by the presence of the visible symbols that
break the ABI.

This is part of why I think it may be beneficial to work around broken
libgcc.a on musl's side: the breakage is subtle when it happens and
it's hard to convince users that there really is a bug.

Rich

--001a11c2e9309c0e5c04fd5d55b4--