mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Reinoud Koornstra <reinoudkoornstra@gmail.com>
Cc: musl@lists.openwall.com
Subject: Re: where to find musl-gcc wrapper script
Date: Mon, 17 Jun 2019 19:30:23 -0400	[thread overview]
Message-ID: <20190617233023.GK1506@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAAA5faGGamErCxKmHk6XM2T7nNHGRt=xNWit-Dzv6Fpbtag-uw@mail.gmail.com>

On Mon, Jun 17, 2019 at 03:49:19PM -0700, Reinoud Koornstra wrote:
> Hello Everyone,
> I did get the sources and build from musl-cross-gcc at github.com.
> Building works fine, however, I cannot find the musl-gcc script to compile.

The musl-gcc wrapper script is for repurposing an existing host
toolchain for a different libc (glibc) to use it with musl. You don't
use it with a proper cross compiler toolchain or on a musl-native
system. The output of musl-cross-make will be a set of utilities
prefixed with the target tuple, e.g. x86_64-linux-musl-gcc, etc., in
the bin directory under wherever you installed the cross toolchain.

Rich


  reply	other threads:[~2019-06-17 23:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17 22:49 Reinoud Koornstra
2019-06-17 23:30 ` Rich Felker [this message]
2019-06-18  0:54   ` Reinoud Koornstra
2019-06-18  2:30     ` Reinoud Koornstra
2019-06-18  2:47       ` Rich Felker
2019-06-18  3:28         ` Reinoud Koornstra
2019-06-18 17:49           ` Rich Felker
2019-06-18 18:27             ` Reinoud Koornstra
2019-06-18 18:43               ` Rich Felker
2019-06-18 21:19                 ` Reinoud Koornstra
2019-06-18 21:37                   ` Rich Felker
2019-06-18 21:49                     ` Reinoud Koornstra
2019-06-18 21:58                       ` Rich Felker
2019-06-18 22:54                         ` Reinoud Koornstra

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=20190617233023.GK1506@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    --cc=reinoudkoornstra@gmail.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).