darkkirb/old-cross-binutils
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

PR 10380

Browse source 
* README: Document use of LDFLAGS="--static".
This commit is contained in:
Nick Clifton 2009-07-14 07:43:18 +00:00
parent 650b89be7e
commit 1aa604e175
2 changed files with 17 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
binutils/ChangeLog
View file

@ -1,3 +1,8 @@
2009-07-14 Nick Clifton <nickc@redhat.com>
PR 10380
* README: Document use of LDFLAGS="--static".
2009-07-10 H.J. Lu <hongjiu.lu@intel.com>
* Makefile.am: Run "make dep-am".

13
binutils/README
View file

@ -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.