Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Tue, 29 Jan 2013 19:43:58 -0800 (PST)
From: idunham@...abit.com
To: musl@...ts.openwall.com
Subject: Re: Using musl in a cross-compiling environment

> 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.

Only gcc needs the -spec line; ld gets parameters from gcc, cpp is no
longer used anywhere, and nothing else cares at all.

So basically, you should be able to go:
export REALGCC=arm-none-linux-gnueabi CC=musl-gcc

although, you might want a patched version of musl-gcc that defaults to
that compiler.

Option 2 is using the musl-cross toolchain instead.


Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.