X-Git-Url: http://nsz.repo.hu/git/?p=musl;a=blobdiff_plain;f=INSTALL;h=5c923ee59df8e55696e177c7b266da28f206ab14;hp=f39d627413940dc9c8e71fc7d5361e34972caf32;hb=99a2af6f45b356324e99acf0da809ca416eed0de;hpb=a23563024fc75a85af955ca203e26c52f939b414

diff --git a/INSTALL b/INSTALL
index f39d6274..5c923ee5 100644
--- a/INSTALL
+++ b/INSTALL
@@ -19,7 +19,7 @@ First, some prerequisites:
   you don't need threads or POSIX 2008 features, even 2.4 is probably
   okay.
 
-- A supported CPU architecture (currently i386, x86_64, or arm).
+- A supported CPU architecture (currently i386, x86_64, arm, or mips).
 
 - If you want to use dynamic linking, it's recommended that you have
   permissions to write to /lib and /etc. Otherwise your binaries will
@@ -76,14 +76,9 @@ musl-gcc hello.c
 ./a.out
 
 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-$ARCH.so.1. 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 ...
-