From: John Mudd <johnbmudd@gmail.com>
To: musl <musl@lists.openwall.com>
Subject: Re: 32 bit musl?
Date: Sat, 8 Oct 2016 21:55:42 -0400 [thread overview]
Message-ID: <CAGDMk9HiUU4Jqz4RURO82_jc9bzSkOepFJfa1B0AXP6rcs6hmg@mail.gmail.com> (raw)
In-Reply-To: <CAGDMk9H3Gwj1NMCOhiCJjGc0zrXj-_+i12z6jBS6V=zCeepWNw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]
Many thanks for the help, Shiz and Rich! I've built gcc from source before
but it's a chore. Rich's musl-cross-make was magical. Much better solution
than using a 32-bit VM.
All I need were these steps. The first two should be obvious but they
tripped me up.
Make sure gcc AND g++ are installed.
unset CC
unzip musl-cross-make-master.zip
cd musl-cross-make-master
make TARGET=i686-linux-musl OUTPUT=$(pwd).install -j6 install
So this builds 32-bit executables that use musl libs. It kills two birds
with one stone. That's great.
But it appears to expect musl libc to be installed in /lib for dynamically
linked executables. That's not an option for me. Is there a way I can
override this?
On Wed, Oct 5, 2016 at 6:20 PM, John Mudd <johnbmudd@gmail.com> wrote:
> ...
> 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
>
[-- Attachment #2: Type: text/html, Size: 1784 bytes --]
next prev parent reply other threads:[~2016-10-09 1:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 22:20 John Mudd
2016-10-05 23:02 ` Rich Felker
2016-10-06 0:24 ` Shiz
2016-10-06 0:33 ` Rich Felker
2016-10-06 7:21 ` Jens Staal
2016-10-06 21:32 ` Rich Felker
2016-10-09 1:55 ` John Mudd [this message]
2016-10-09 9:36 ` Laurent Bercot
2016-10-09 14:29 ` John Mudd
2016-10-09 14:44 ` Szabolcs Nagy
2016-10-09 15:10 ` Bobby Bingham
2016-10-09 16:08 ` 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=CAGDMk9HiUU4Jqz4RURO82_jc9bzSkOepFJfa1B0AXP6rcs6hmg@mail.gmail.com \
--to=johnbmudd@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).