X-Git-Url: http://drtracing.org/?a=blobdiff_plain;f=binutils%2FREADME;h=9b5e622480685f832ceae29fbe493edd50d3587b;hb=0ac553107c601cc9c4c340338e0fc7e0ce8375cc;hp=5bc2508b39f16365cd497bc9f372f534a7fb6ae8;hpb=01f0fe5e0450edf168c1f612feb93cf588e4e7ea;p=deliverable%2Fbinutils-gdb.git

diff --git a/binutils/README b/binutils/README
index 5bc2508b39..9b5e622480 100644
--- a/binutils/README
+++ b/binutils/README
@@ -13,6 +13,15 @@ There are README and NEWS files in most of the program sub-directories
 which give more information about those specific programs.
 
 
+Copyright Notices
+=================
+
+Copyright years on binutils source files may be listed using range
+notation, e.g., 1991-2012, indicating that every year in the range,
+inclusive, is a copyrightable year that could otherwise be listed
+individually.
+
+
 Unpacking and Installation -- quick overview
 ============================================
 
@@ -48,7 +57,7 @@ By default, the binutils will be configured to support the system on
 which they are built.  When doing cross development, use the --target
 configure option to specify a different target, eg:
 
-	./configure --target=foo-elf        
+	./configure --target=foo-elf
 
 The --enable-targets option adds support for more binary file formats
 besides the default.  List them as the argument to --enable-targets,
@@ -64,7 +73,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 +88,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.
 
@@ -159,7 +179,7 @@ Always mention the version number you are running; this is printed by
 running any of the binutils with the --version option.  We appreciate
 reports about bugs, but we do not promise to fix them, particularly so
 when the bug report is against an old version.  If you are able, please
-consider building the latest tools from CVS to check that your bug has
+consider building the latest tools from git to check that your bug has
 not already been fixed.
 
 When reporting problems about gas and ld, it's useful to provide a
@@ -271,3 +291,9 @@ unneeded objects and libraries:
 
 If you have any problems or questions about the binutils on VMS, feel
 free to mail me at kkaempf@rmi.de.
+
+Copyright (C) 2012-2020 Free Software Foundation, Inc.
+
+Copying and distribution of this file, with or without modification,
+are permitted in any medium without royalty provided the copyright
+notice and this notice are preserved.