From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/5827 Path: news.gmane.org!not-for-mail From: u-igbb@aetey.se Newsgroups: gmane.linux.lib.musl.general Subject: Re: compiling musl on x86_64 linux with ppc Date: Wed, 13 Aug 2014 14:56:08 +0200 Message-ID: <20140813125607.GK5170@example.net> References: <20140813091843.GD5170@example.net> <20140813123832.GK12888@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1407934600 2268 80.91.229.3 (13 Aug 2014 12:56:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 13 Aug 2014 12:56:40 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-5833-gllmg-musl=m.gmane.org@lists.openwall.com Wed Aug 13 14:56:32 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 1XHY6P-0006x1-PV for gllmg-musl@plane.gmane.org; Wed, 13 Aug 2014 14:56:29 +0200 Original-Received: (qmail 2019 invoked by uid 550); 13 Aug 2014 12:56:28 -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 2008 invoked from network); 13 Aug 2014 12:56:28 -0000 X-T2-Spam-Status: No, hits=0.0 required=5.0 Received-SPF: none receiver=mailfe03.swip.net; client-ip=77.247.181.164; envelope-from=u-igbb@aetey.se Content-Disposition: inline In-Reply-To: <20140813123832.GK12888@brightrain.aerifal.cx> User-Agent: Mutt/1.5.23 (2014-03-12) Xref: news.gmane.org gmane.linux.lib.musl.general:5827 Archived-At: On Wed, Aug 13, 2014 at 08:38:32AM -0400, Rich Felker wrote: > > I am trying to compile musl 1.1.4 on x86_64 with ppc (latest from cvs). > > Are you sure it's latest? If you're using a snapshot there are > multiple branches (iirc 1.0.DEVEL and 1.1.DEVEL or something like > that) and the old one is very outdated and broken. I did my best to locate the latest one, it seems to present itself as 1.1.0.DEVEL > > src/aio/aio_readwrite.c, line 23: compiler error: unsupported xasm constraint r11 > > error: XXXXX/libexec/ccom terminated with status 1 > > make: *** [src/aio/aio_readwrite.o] Error 1 > > ----------- > > > > Is there any way around this, short of adding the register assignment > > functionality to the compiler? > > Just use the #ifdef __clang__ branch of the code which handles the > same brokenness in clang. :-) According to Anders Magnusson (he replied on pcc-list) it is sufficient to refer to r11 as %r11 to make it work. He thinks otherwise of adding the alias r11 for %r11 in pcc. Indeed, with a change of all "r11" to "%r11" in arch/x86_64/syscall_arch.h the compilation went through without disabling the separate __syscallN(). My goal is a musl-based selfcontained pcc toolchain. I'd like to also have a tcc-based one but musl seems to be too hard a target for tcc yet :( sigh. Rune