[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161006003342.GN19318@brightrain.aerifal.cx>
Date: Wed, 5 Oct 2016 20:33:42 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: 32 bit musl?
On Thu, Oct 06, 2016 at 02:24:43AM +0200, Shiz wrote:
> As Rich noted, a cross-compiler is the easy way out here - GCC multilib has a number of assumptions that break under musl and likely elsewhere.
> Since you seem unsure how to compile one, I’d recommend musl-cross-make[1].
> You only need to edit a single variable in config.mak and run 'make && make install' to get a working toolchain.
You can actually even skip editing/making config.mak with current
versions of mcm. I typically just do something like:
make TARGET=i686-linux-musl OUTPUT=[whatever] -j4 install
Rich
> [1]: https://github.com/richfelker/musl-cross-make
>
> > On 06 Oct 2016, at 00:20, John Mudd <johnbmudd@...il.com> wrote:
> >
> > I've been using musl on a 32-bit Linux to build 32-bit apps to run
> > on 32 and 64-bit Linux machines. That works well.
> >
> > I upgraded to a 64 bit development box. I've assumed I would just
> > need to use -m32 option and I could still build 32 bit apps on my
> > 64 bit machine. I tried it but it tries to mix 32 & 64 bit code. I
> > guess I was naive.
> >
> > It looks like I should build a cross compiler? I see several
> > suggestions on how to do this so I'm not confident this will work
> > well. Or would it be easier if I just installed a 32 bit Linux in
> > a VM just for building 32 bit apps with musl?
> >
> > John
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.
