mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Cc: James Larrowe <larrowe.semaj11@gmail.com>
Subject: Re: Re: [PATCH] Enable multilib support when building with musl-gcc
Date: Thu, 21 Feb 2019 15:44:57 +0100	[thread overview]
Message-ID: <20190221144456.GW21289@port70.net> (raw)
In-Reply-To: <CAEfvv4J+Wx5JbWZj758_5-egQz_ke55dvpVxZfATNz_v5xQnMA@mail.gmail.com>

* James Larrowe <larrowe.semaj11@gmail.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@gmail.com>
> wrote:
> 
> > Somewhat incomplete; enables using 32-bit musl-gcc
> > on a 64-bit system
> >
> > Signed-off-by: James Larrowe <larrowe.semaj11@gmail.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
> >
> >


  reply	other threads:[~2019-02-21 14:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30 21:38 James Larrowe
2019-02-21 14:22 ` James Larrowe
2019-02-21 14:44   ` Szabolcs Nagy [this message]
2019-02-21 14:50     ` James Larrowe
2019-02-21 15:26       ` Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190221144456.GW21289@port70.net \
    --to=nsz@port70.net \
    --cc=larrowe.semaj11@gmail.com \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).