diff options
| author | Shiz <hi@shiz.me> | 2015-06-28 23:08:20 +0200 |
|---|---|---|
| committer | Rich Felker <dalias@aerifal.cx> | 2015-07-06 19:37:06 -0400 |
| commit | f8db6f74b2c74a50c4dec7e30be5215f0e2c37a6 (patch) | |
| tree | f47f964d740d59c848336c4da765c3fd8752d5e8 /crt/crt1.c | |
| parent | b3cd7d13fe630ba1847326242525298e361018c1 (diff) | |
| download | musl-f8db6f74b2c74a50c4dec7e30be5215f0e2c37a6.tar.gz musl-f8db6f74b2c74a50c4dec7e30be5215f0e2c37a6.tar.bz2 musl-f8db6f74b2c74a50c4dec7e30be5215f0e2c37a6.tar.xz musl-f8db6f74b2c74a50c4dec7e30be5215f0e2c37a6.zip | |
build: fix musl-targeting toolchain test
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.
Diffstat (limited to 'crt/crt1.c')
0 files changed, 0 insertions, 0 deletions