Merge commit 'upstream/2.20'

[msp430-binutils.git] / binutils / README

diff --git a/binutils/README b/binutils/README
index 5bc2508b39f16365cd497bc9f372f534a7fb6ae8..fc474a5410c976a886efa452217313231c6415cb 100644 (file)
--- a/binutils/README
+++ b/binutils/README
@@ -64,7 +64,7 @@ On 32-bit hosts though, this support will be restricted to 32-bit
 target unless the --enable-64-bit-bfd option is also used:
 
        ./configure --enable-64-bit-bfd --enable-targets=all
-       
+
 You can also specify the --enable-shared option when you run
 configure.  This will build the BFD and opcodes libraries as shared
 libraries.  You can use arguments with the --enable-shared option to
@@ -79,6 +79,17 @@ binaries, you may have to set an environment variable, normally
 LD_LIBRARY_PATH, so that the system can find the installed libbfd
 shared library.
 
+On hosts that support shared system libraries the binutils will be
+linked against them.  If you have static versions of the system
+libraries installed as well and you wish to create static binaries
+instead then use the LDFLAGS environment variable,  like this:
+
+  ../binutils-XXX/configure LDFLAGS="--static" [more options]
+
+Note: the two dashes are important.  The binutils make use of the
+libtool script which has a special interpretation of "-static" when it
+is in the LDFLAGS environment variable.
+
 To build under openVMS/AXP, see the file makefile.vms in the top level
 directory.