From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/13837 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Re: [PATCH] Enable multilib support when building with musl-gcc Date: Thu, 21 Feb 2019 10:26:12 -0500 Message-ID: <20190221152612.GG23599@brightrain.aerifal.cx> References: <20190130213815.19267-1-larrowe.semaj11@gmail.com> <20190221144456.GW21289@port70.net> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="19337"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-13853-gllmg-musl=m.gmane.org@lists.openwall.com Thu Feb 21 16:26:27 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1gwqF1-0004w4-1f for gllmg-musl@m.gmane.org; Thu, 21 Feb 2019 16:26:27 +0100 Original-Received: (qmail 11508 invoked by uid 550); 21 Feb 2019 15:26:25 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 11484 invoked from network); 21 Feb 2019 15:26:24 -0000 Content-Disposition: inline In-Reply-To: Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:13837 Archived-At: On Thu, Feb 21, 2019 at 09:50:04AM -0500, James Larrowe wrote: > It was actually intended to fix building musl with "gcc -m32". If you run > "CC='gcc -m32' ./configure && make && sudo make install" and try to run > `musl-gcc`, it doesn't work and causes some "Incompatible architcture" > errors. If there's any way I can make this better, please let me know and > I'll resend the patch. When generating the musl-gcc wrapper, the -m32 is supposed to get inserted into it if -m32 was included in $CC. It looks like there's some reason this doesn't work without some linker flags also being passed, and the musl-gcc.specs file is overriding a link spec in a way that loses them. I'm not sure what the right fix it. It might be using the specfile mechanism to rename/clone an existing spec then including it at the beginning of the new one, with options at the end to override, rather than replacing the old one, but I'm not sure if that works here. Rich > On Thu, Feb 21, 2019 at 9:44 AM Szabolcs Nagy wrote: > > > * James Larrowe [2019-02-21 09:22:26 -0500]: > > > Ping. Is there anything wrong with this? It works for me. > > > > it breaks all targets that musl supports except x86_64 > > > > a multilib toolchain does not have separate include paths > > for different abis so even on x86_64, -m32 or -mx32 > > would use the wrong headers. > > > > > On Wed, Jan 30, 2019 at 4:38 PM James Larrowe > > > > > wrote: > > > > > > > Somewhat incomplete; enables using 32-bit musl-gcc > > > > on a 64-bit system > > > > > > > > Signed-off-by: James Larrowe > > > > --- > > > > tools/musl-gcc.specs.sh | 4 +++- > > > > 1 file changed, 3 insertions(+), 1 deletion(-) > > > > > > > > diff --git a/tools/musl-gcc.specs.sh b/tools/musl-gcc.specs.sh > > > > index 30492574..a73e6656 100644 > > > > --- a/tools/musl-gcc.specs.sh > > > > +++ b/tools/musl-gcc.specs.sh > > > > @@ -23,7 +23,9 @@ libgcc.a%s %:if-exists(libgcc_eh.a%s) > > > > crtendS.o%s $libdir/crtn.o > > > > > > > > *link: > > > > --dynamic-linker $ldso -nostdlib %{shared:-shared} %{static:-static} > > > > %{rdynamic:-export-dynamic} > > > > +-dynamic-linker $ldso -nostdlib %{shared:-shared} %{static:-static} \ > > > > + %{rdynamic:-export-dynamic} %{m64:-melf_x86_64} > > %{mx32:-melf32_x86_64} \ > > > > + %{m32:-melf_i386} > > > > > > > > *esp_link: > > > > > > > > -- > > > > 2.20.1 > > > > > > > > > >