From 1aa604e1750feb1f2dfec8a3418875f3a7bba68d Mon Sep 17 00:00:00 2001 From: Nick Clifton Date: Tue, 14 Jul 2009 07:43:18 +0000 Subject: [PATCH] PR 10380 * README: Document use of LDFLAGS="--static". --- binutils/ChangeLog | 5 +++++ binutils/README | 13 ++++++++++++- 2 files changed, 17 insertions(+), 1 deletion(-) diff --git a/binutils/ChangeLog b/binutils/ChangeLog index 58f8bc8a54..91ea69cfe5 100644 --- a/binutils/ChangeLog +++ b/binutils/ChangeLog @@ -1,3 +1,8 @@ +2009-07-14 Nick Clifton + + PR 10380 + * README: Document use of LDFLAGS="--static". + 2009-07-10 H.J. Lu * Makefile.am: Run "make dep-am". diff --git a/binutils/README b/binutils/README index 5bc2508b39..fc474a5410 100644 --- 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.