From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/5417 Path: news.gmane.org!not-for-mail From: Rob Landley Newsgroups: gmane.linux.lib.musl.general Subject: Re: glfw - x11 and opengl Date: Mon, 07 Jul 2014 19:38:26 -0500 Message-ID: <53BB3D82.9070506@landley.net> References: <20140703205039.GB179@brightrain.aerifal.cx> <53B5F1D7.4000402@skarnet.org> <1404441610.1648.0.camel@gandalf.lan.sholland.net> <20140704032546.GD179@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1404779938 10799 80.91.229.3 (8 Jul 2014 00:38:58 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 8 Jul 2014 00:38:58 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-5422-gllmg-musl=m.gmane.org@lists.openwall.com Tue Jul 08 02:38:52 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 1X4JQp-0002HU-QJ for gllmg-musl@plane.gmane.org; Tue, 08 Jul 2014 02:38:51 +0200 Original-Received: (qmail 13988 invoked by uid 550); 8 Jul 2014 00:38: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 13980 invoked from network); 8 Jul 2014 00:38:49 -0000 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=lXbaPeufZMYaI1iaEo3TEgUfgAswomTb5wbLJ4IjKYk=; b=ZlbJfI2Ej/mKpLF++DoCzn7yOWC3famjeiePnWVCLgwVV5MfV0nZU4YkGFQ78Qn9K5 2/JdLTfdCDA9UreIpyrD5NiTZR6RNO9Y2fjEF/N7Z5UMAe72B3ElJm/9TeHhCVGqcm1o l0qLT5M7l9RRU59K89FNVrK/1G57zoPY9uNg/UdSBnDypce+vy6hk2EN6WGinT3e11bo sXDCvzOmhWLYKzVkK9bxYRl2/0Sjpk47JjxEGwAjYjxGji1M3RewH3En3RG+rcqoM1/U mPDzLloVqBG1436CwFGM1cOB7kfQxC+OAgNW+dry9mrkfahqCpH8hK7nm5Vlr1gy9LBp 49LQ== X-Gm-Message-State: ALoCoQmDOBDu960TuvXzvhCaaBF8jivRWAb1Abz8yW2NGFgLSBK/sM6uZmW4gmjwd5HbQvmBHwRv X-Received: by 10.60.103.76 with SMTP id fu12mr34937846oeb.34.1404779917243; Mon, 07 Jul 2014 17:38:37 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 In-Reply-To: <20140704032546.GD179@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:5417 Archived-At: On 07/03/14 22:25, 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 > 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. Dynamic linking is indeed broken. Haven't tracked down why yet. (hello-dynamic works on i686, segfaults on mips.) Static building seems to work reasonably well though. No sparc support, but I only ever got 32 bits working there anyway. (Less sad about the lack of m68k support since there _still_ wasn't a working qemu for that last I checked.) > BTW regarding the libgcc.a issue, since it seems to be common in > bootstrapping, it might be worth working around it in the musl build > process by using -Wl,--exclude-libs,libgcc.a if this option is > supported by the linker. Which libgcc.a issue? I hit a couple different ones, but I think they're fixed now? > Anyway back to the point, it's great to see musl making it into > Aboriginal! Thanks. Sorry it took so long but it's _fiddly_ getting a new toolchain to work. And I'm sure something else is still lurking somewhere... > Rich Rob