From: Andre Renaud <andre@bluewatersys.com>
To: musl@lists.openwall.com
Subject: Using musl in a cross-compiling environment
Date: Wed, 30 Jan 2013 13:03:18 +1300 [thread overview]
Message-ID: <CAPfzE3bMxmzfHJgNK7UZuYvobAXCpBRxbXBt-+tuwE128yLL4w@mail.gmail.com> (raw)
Hi,
We're investigating moving some of our future projects over to using
musl. All of our development is done in a cross-compiling environment
(hosted on x86_64, targeting various ARM platforms). We've done some
preliminary testing, and it has all gone well. However when we come to
start cross compiling third party packages, we generally run into
various minor issues. Mostly it is around getting configure to work
properly, pick up the correct compiler, and pass through the
appropriate flags. How do you guys normally cope with this? I know of
the musl-gcc command, but unfortunately when you're cross compiling
you generally need to have all of your commands with a similar prefix
(ie: arm-none-linux-gnueabi-gcc, arm-none-linux-gnueabi-strip etc...)
I thought of creating a bin directory with a bunch of scripts, which
have the same name as the original commands, and simply put the
'-spec' line in there, similar to musl-gcc.
Does anyone have any comments on how this is best achieved?
Regards,
Andre
next reply other threads:[~2013-01-30 0:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 0:03 Andre Renaud [this message]
2013-01-30 3:43 ` idunham
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=CAPfzE3bMxmzfHJgNK7UZuYvobAXCpBRxbXBt-+tuwE128yLL4w@mail.gmail.com \
--to=andre@bluewatersys.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).