Add paragraph about using --disable-nls

[deliverable/binutils-gdb.git] / binutils / README

diff --git a/binutils/README b/binutils/README
index e51b2a2cb55ddfaa76b9cbe17ceecaa48650912a..936f25f85ef65d88b738093d36b470f8c33307b1 100644 (file)
--- a/binutils/README
+++ b/binutils/README
@@ -18,7 +18,7 @@ Unpacking and Installation -- quick overview
 
 When you unpack the binutils archive file, you will get a directory
 called something like `binutils-XXX', where XXX is the number of the
 
 When you unpack the binutils archive file, you will get a directory
 called something like `binutils-XXX', where XXX is the number of the

-release.  (Probably 2.11.2 or higher).  This directory contains
+release.  (Probably 2.13 or higher).  This directory contains

 various files and sub-directories.  Most of the files in the top
 directory are for information and for configuration.  The actual
 source code is in sub-directories.
 various files and sub-directories.  Most of the files in the top
 directory are for information and for configuration.  The actual
 source code is in sub-directories.


@@ -83,6 +83,18 @@ To build under openVMS/AXP, see the file makefile.vms in the top level
 directory.
 
 
 directory.
 
 

+Native Language Support
+=======================
+
+By default Native Language Support will be enabled for binutils.  On
+some systems however this support is not present and can lead to error
+messages such as "undefined reference to `libintl_gettext'" when
+building there tools.  If that happens the NLS support can be disabled
+by adding the --disable-nls switch to the configure line like this:
+
+       ../binutils-XXX/configure --disable-nls
+
+

 If you don't have ar
 ====================
 
 If you don't have ar
 ====================
 


@@ -100,7 +112,7 @@ ${MAKE} $* all-bfd
 cd binutils
 MAKE="${MAKE_PROG}"
 export MAKE
 cd binutils
 MAKE="${MAKE_PROG}"
 export MAKE

-${MAKE} $* ar_DEPENDENCIES= ar_LDADD='../bfd/*.o `cat ../libiberty/required-list ../libiberty/needed-list | sed -e "s,\([^ ][^ ]*\),../libiberty/\1,g"` `if test -f ../intl/gettext.o; then echo '../intl/*.o'; fi`' ar
+${MAKE} $* ar_DEPENDENCIES= ar_LDADD='../bfd/*.o ../libiberty/*.o `if test -f ../intl/gettext.o; then echo '../intl/*.o'; fi`' ar

 
 This script will build an ar program in binutils/ar.  Move binutils/ar
 into a directory on your PATH.  After doing this, you can run make as
 
 This script will build an ar program in binutils/ar.  Move binutils/ar
 into a directory on your PATH.  After doing this, you can run make as


@@ -110,7 +122,7 @@ the ranlib program in order to build the distribution.
 Porting
 =======
 
 Porting
 =======
 

-Binutils-2.11 supports many different architectures, but there
+Binutils-2.13 supports many different architectures, but there

 are many more not supported, including some that were supported
 by earlier versions.  We are hoping for volunteers to improve this
 situation.
 are many more not supported, including some that were supported
 by earlier versions.  We are hoping for volunteers to improve this
 situation.


@@ -118,14 +130,14 @@ situation.
 The major effort in porting binutils to a new host and/or target
 architecture involves the BFD library.  There is some documentation
 in ../bfd/doc.  The file ../gdb/doc/gdbint.texinfo (distributed
 The major effort in porting binutils to a new host and/or target
 architecture involves the BFD library.  There is some documentation
 in ../bfd/doc.  The file ../gdb/doc/gdbint.texinfo (distributed

-with gdb-4.x) may also be of help.
+with gdb-5.x) may also be of help.

 
 Reporting bugs
 ==============
 
 Send bug reports and patches to:
 
 
 Reporting bugs
 ==============
 
 Send bug reports and patches to:
 

-   bug-gnu-utils@gnu.org.
+   bug-binutils@gnu.org.

 
 Always mention the version number you are running; this is printed by
 running any of the binutils with the --version option.  We appreciate
 
 Always mention the version number you are running; this is printed by
 running any of the binutils with the --version option.  We appreciate