README revision 38889
1These are the GNU binutils. These are utilities of use when dealing 2with object files. 3 4The linker (ld) is in a separate directory, which should be ../ld. 5Linker-specific notes are in ../ld/README. 6 7As of version 2.5, the assembler (as) is also included in this package, in 8../gas. Assembler-specific notes can be found in ../gas/README. 9 10Recent changes are in ./NEWS, ../ld/NEWS, and ../gas/NEWS. 11 12Unpacking and Installation -- quick overview 13============================================ 14 15When you unpack the binutils-2.9.tar.gz file, you'll get a directory 16called something like `binutils-2.9', which contains various files and 17directories. Most of the files in the top directory are for 18information and for configuration. The actual source code is in 19subdirectories. 20 21To build binutils, you can just do: 22 23 cd binutils-2.9 24 ./configure [options] 25 make 26 make install # copies the programs files into /usr/local/bin 27 # by default. 28 29This will configure and build all the libraries as well as the 30assembler, the binutils, and the linker. 31 32If you have GNU make, we recommend building in a different directory: 33 34 mkdir objdir 35 cd objdir 36 ../binutils-2.9/configure [options] 37 make 38 make install 39 40This relies on the VPATH feature of GNU make. 41 42By default, the binutils will be configured to support the system on 43which they are built. When doing cross development, use the --target 44configure option to specify a different target. 45 46The --enable-targets option adds support for more binary file formats 47besides the default. List them as the argument to --enable-targets, 48separated by commas. For example: 49 50 ./configure --enable-targets=sun3,rs6000-aix,decstation 51 52The name 'all' compiles in support for all valid BFD targets (this was 53the default in releases before 2.3): 54 55 ./configure --enable-targets=all 56 57You can also specify the --enable-shared option when you run 58configure. This will build the BFD and opcodes libraries as shared 59libraries. You can use arguments with the --enable-shared option to 60indicate that only certain libraries should be built shared; for 61example, --enable-shared=bfd. The only potential shared libraries in 62a binutils release are bfd and opcodes. 63 64The binutils will be linked against the shared libraries. The build 65step will attempt to place the correct library in the runtime search 66path for the binaries. However, in some cases, after you install the 67binaries, you may have to set an environment variable, normally 68LD_LIBRARY_PATH, so that the system can find the installed libbfd 69shared library. 70 71To build under openVMS/AXP, see the file makefile.vms in the top level 72directory. 73 74If you don't have ar 75==================== 76 77If your system does not already have an ar program, the normal 78binutils build process will not work. In this case, run configure as 79usual. Before running make, run this script: 80 81#!/bin/sh 82MAKE=${MAKE-make} 83${MAKE} $* AR=true all-libiberty 84${MAKE} $* AR=true all-bfd 85cd binutils 86${MAKE} $* ADDL_DEPS='$(BULIBS)' ADDL_LIBS='$(BULIBS) ../bfd/*.o `cat ../libiberty/required-list ../libiberty/needed-list | sed -e "s,\([^ ][^ ]*\),../libiberty/\1,g"`' ar 87 88This script will build an ar program in binutils/ar. Move binutils/ar 89into a directory on your PATH. After doing this, you can run make as 90usual to build the complete binutils distribution. You do not need 91the ranlib program in order to build the distribution. 92 93Porting 94======= 95 96Binutils-2.9 supports many different architectures, but there 97are many more not supported, including some that were supported 98by earlier versions. We are hoping for volunteers to 99improve this situation. 100 101The major effort in porting binutils to a new host and/or target 102architecture involves the BFD library. There is some documentation 103in ../bfd/doc. The file ../gdb/doc/gdbint.texinfo (distributed 104with gdb-4.x) may also be of help. 105 106Reporting bugs 107============== 108 109Send bug reports and patches to bug-gnu-utils@gnu.org. Always mention 110the version number you are running; this is printed by running any of 111the binutils with the --version option. We appreciate reports about 112bugs, but we do not promise to fix them. 113 114Testing 115======= 116 117Testing this release of the binutils requires an unreleased version of 118dejagnu. There is a dejagnu snapshot available at 119 ftp://ftp.cygnus.com/pub/binutils 120which may be used for testing. 121 122Maintenance 123=========== 124 125The configure and Makefile.in files in the subdirectories are 126generated by autoconf and automake, respectively. The libtool package 127is also required. In order to make the generation rules fire 128automatically, you must configure with the --enable-maintainer-mode 129option. This option is not the default in order to avoid problems on 130systems which have out of date versions of autoconf or automake 131installed. The generated files in this release were built with 132unreleased versions of autoconf, automake, and libtool. You can find 133snapshots of the appropriate sources at 134 ftp://ftp.cygnus.com/pub/binutils 135