mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Re: [J-core] musl-cross-make / litecross improvements
Date: Wed, 4 May 2016 13:52:43 +0200	[thread overview]
Message-ID: <20160504115242.GX22574@port70.net> (raw)
In-Reply-To: <5729DC9A.7090807@skarnet.org>

* Laurent Bercot <ska-dietlibc@skarnet.org> [2016-05-04 13:27:22 +0200]:
> On 04/05/2016 13:10, Szabolcs Nagy wrote:
> >>Still no native toolchains. :)
> >>
> >
> >for native you need a musl based host
> >at which point you can use a musl based
> >distro that provides native toolchains.
> 
>  Huh? And what if you *are* the musl-based distro and need to build said
> native toolchain?
>  I'm surprised to hear you, of all people, mentioning "relying on your distro"
> as a solution. :P
> 
>  I've had success, with the previous iteration of musl-cross-make,
> building native toolchains via disabling --host in COMMON_CONFIG
> (and compiling gmp, mpfr and mpc for the target first). In other words,
> host=target (even if build!=host). They're still considered cross-toolchains,
> as in the binaries are prefixed with ${ARCH}- , but they work. I'm not sure
> whether it's still possible with the current version of mcm.

yes, that works, you can cross build a toolchain with host==target
and then it will be a native toolchain.

(i havent tried it with mcm, but first you build a cross toolchain
and then you should be able to use that to build the native one.)

what i meant was that you can only use that toolchain in a native
musl environment and for most users that's a distro with its own
toolchain (otherwise you have to build busybox etc yourself).


  reply	other threads:[~2016-05-04 11:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-03  4:48 Rich Felker
2016-05-03 11:39 ` Szabolcs Nagy
2016-05-03 18:02   ` Rich Felker
2016-05-03 20:16     ` Szabolcs Nagy
2016-05-03 21:57       ` Szabolcs Nagy
2016-05-04  0:16         ` Rich Felker
2016-05-04  3:53         ` Rich Felker
2016-05-04  8:15           ` Szabolcs Nagy
2016-05-06  5:14         ` Rich Felker
2016-05-04  9:28 ` [J-core] " Rob Landley
2016-05-04 11:10   ` Szabolcs Nagy
2016-05-04 11:27     ` Laurent Bercot
2016-05-04 11:52       ` Szabolcs Nagy [this message]
2016-05-04 16:33   ` Rich Felker
2016-05-04 16:48     ` Daniel Cegiełka
2016-05-04 17:16     ` Szabolcs Nagy
2016-05-04 18:09       ` Rich Felker
2016-05-04 17:54     ` Rich Felker
2016-05-05 22:43 ` Patrick Oppenlander
2016-05-06  2:44   ` Rich Felker
2016-05-06  6:03     ` Patrick Oppenlander
2016-05-06 20:49     ` Szabolcs Nagy
2016-05-08 23:04       ` Patrick Oppenlander

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=20160504115242.GX22574@port70.net \
    --to=nsz@port70.net \
    --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).