mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Isaac Dunham <ibid.ag@gmail.com>
To: musl@lists.openwall.com
Subject: Re: [PATCH v3 2/3] build: fix musl-targeting toolchain test
Date: Mon, 29 Jun 2015 07:35:21 -0700	[thread overview]
Message-ID: <20150629143521.GB1861@newbook> (raw)
In-Reply-To: <1435525701-64741-2-git-send-email-hi@shiz.me>

On Sun, Jun 28, 2015 at 11:08:20PM +0200, Shiz wrote:
> the old test was broken in that it would never fail on a toolchains built
> without dynamic linking support, leading to the wrapper script possibly being
> installed on compilers that do not support it. in addition, the new test is
> portable across compilers: the old test only worked on GCC.
> 
> the new test works by testing whether the toolchain libc defines __GLIBC__:
> most non-musl Linux libc's do define this for compatibility even when they
> are not glibc, so this is a safe bet to check for musl. in addition, the
> compiler runtime would need to have a somewhat glibc-compatible ABI in the
> first place, so any non-glibc compatible libc's compiler runtime might not
> work. it is safer to disable these cases by default and have the user enable
> the wrappers manually there using --enable-wrapper if they certain it works.

A long while back, someone reported successfully using a FreeBSD gcc
to build musl, then using that + musl-gcc to build programs that
worked using the Linux emulation layer on FreeBSD.
They submitted a patch with a BSD makefile at that point.

Thanks,
Isaac Dunham



  reply	other threads:[~2015-06-29 14:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-28 21:08 [PATCH v3 1/3] build: overhaul wrapper script system for multiple wrapper support Shiz
2015-06-28 21:08 ` [PATCH v3 2/3] build: fix musl-targeting toolchain test Shiz
2015-06-29 14:35   ` Isaac Dunham [this message]
2015-06-29 17:30     ` Rich Felker
2015-06-28 21:08 ` [PATCH v3 3/3] add musl-clang, a wrapper for system clang installs Shiz
2015-07-07 19:30   ` Matias A. Fonzo
2015-07-07  0:12 ` [PATCH v3 1/3] build: overhaul wrapper script system for multiple wrapper support 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=20150629143521.GB1861@newbook \
    --to=ibid.ag@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).