[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190221144456.GW21289@port70.net>
Date: Thu, 21 Feb 2019 15:44:57 +0100
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Cc: James Larrowe <larrowe.semaj11@...il.com>
Subject: Re: Re: [PATCH] Enable multilib support when building with
musl-gcc
* James Larrowe <larrowe.semaj11@...il.com> [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 <larrowe.semaj11@...il.com>
> wrote:
>
> > Somewhat incomplete; enables using 32-bit musl-gcc
> > on a 64-bit system
> >
> > Signed-off-by: James Larrowe <larrowe.semaj11@...il.com>
> > ---
> > 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
> >
> >
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
