path: root/INSTALL
diff options
authorRich Felker <>2012-09-07 23:13:55 -0400
committerRich Felker <>2012-09-07 23:13:55 -0400
commitc1a9658bd19245ff0fb52d3da567815d822fb622 (patch)
tree36af789c4a0ebc8a1af3c49eab9edb34f5dbf869 /INSTALL
parent9f65796c35bd93a1de42752ce8af901acfe4b1a4 (diff)
default features: make musl usable without feature test macros
the old behavior of exposing nothing except plain ISO C can be obtained by defining __STRICT_ANSI__ or using a compiler option (such as -std=c99) that predefines it. the new default featureset is POSIX with XSI plus _BSD_SOURCE. any explicit feature test macros will inhibit the default. installation docs have also been updated to reflect this change.
Diffstat (limited to 'INSTALL')
1 files changed, 2 insertions, 13 deletions
diff --git a/INSTALL b/INSTALL
index 720c94ea..5c923ee5 100644
@@ -76,14 +76,9 @@ musl-gcc hello.c
To configure autoconf-based program to compile and link against musl,
-you may wish to use:
+set the CC variable to musl-gcc when running configure, as in:
-CC="musl-gcc -D_GNU_SOURCE" ./configure ...
-Correctly-written build systems should not need -D_GNU_SOURCE as part
-of $CC, but many programs do not use feature-test macros correctly and
-simply assume the compiler will automatically give them the kitchen
-sink, so the above command is an easy workaround.
+CC=musl-gcc ./configure ...
You will probably also want to use --prefix when building libraries to
ensure that they are installed under the musl prefix and not in the
@@ -140,9 +135,3 @@ dynamic linker (program interpreter) is /lib/ld-musl-$ If
you're using static linking only, you might instead check the symbols
and look for anything suspicious that would indicate your old glibc or
uClibc was used.
-When building programs against musl, you may still want to ensure the
-appropriate feature test macros get defined, as in:
-CC="gcc -D_GNU_SOURCE" ./configure ...