| README (77298) | README (89857) |
|---|---|
| 1 README for BINUTILS 2 |
|
| 1These are the GNU binutils. These are utilities of use when dealing | 3These are the GNU binutils. These are utilities of use when dealing |
| 2with object files. | 4with binary files, either object files or executables. These tools 5consist of the linker (ld), the assembler (gas), and the profiler 6(gprof) each of which have their own sub-directory named after them. 7There is also a collection of other binary tools, including the 8disassembler (objdump) in this directory. These tools make use of a 9pair of libraries (bfd and opcodes) and a common set of header files 10(include). |
| 3 | 11 |
| 4The linker (ld) is in a separate directory, which should be ../ld. 5Linker-specific notes are in ../ld/README. | 12There are README and NEWS files in most of the program sub-directories 13which give more information about those specific programs. |
| 6 | 14 |
| 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 | 15 |
| 10Recent changes are in ./NEWS, ../ld/NEWS, and ../gas/NEWS. 11 | |
| 12Unpacking and Installation -- quick overview 13============================================ 14 | 16Unpacking and Installation -- quick overview 17============================================ 18 |
| 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. | 19When you unpack the binutils archive file, you will get a directory 20called something like `binutils-XXX', where XXX is the number of the 21release. (Probably 2.11.2 or higher). This directory contains 22various files and sub-directories. Most of the files in the top 23directory are for information and for configuration. The actual 24source code is in sub-directories. |
| 20 21To build binutils, you can just do: 22 | 25 26To build binutils, you can just do: 27 |
| 23 cd binutils-2.9 | 28 cd binutils-XXX |
| 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 | 29 ./configure [options] 30 make 31 make install # copies the programs files into /usr/local/bin 32 # by default. 33 34This will configure and build all the libraries as well as the 35assembler, the binutils, and the linker. 36 37If you have GNU make, we recommend building in a different directory: 38 39 mkdir objdir 40 cd objdir |
| 36 ../binutils-2.9/configure [options] | 41 ../binutils-XXX/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 | 42 make 43 make install 44 45This relies on the VPATH feature of GNU make. 46 47By default, the binutils will be configured to support the system on 48which they are built. When doing cross development, use the --target |
| 44configure option to specify a different target. | 49configure option to specify a different target, eg: |
| 45 | 50 |
| 51 ./configure --target=foo-elf 52 |
|
| 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 | 53The --enable-targets option adds support for more binary file formats 54besides the default. List them as the argument to --enable-targets, 55separated by commas. For example: 56 57 ./configure --enable-targets=sun3,rs6000-aix,decstation 58 |
| 52The name 'all' compiles in support for all valid BFD targets (this was 53the default in releases before 2.3): | 59The name 'all' compiles in support for all valid BFD targets: |
| 54 55 ./configure --enable-targets=all 56 | 60 61 ./configure --enable-targets=all 62 |
| 63On 32-bit hosts though, this support will be restricted to 32-bit 64target unless the --enable-64-bit-bfd option is also used: 65 66 ./configure --enable-64-bit-bfd --enable-targets=all 67 |
|
| 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 | 68You can also specify the --enable-shared option when you run 69configure. This will build the BFD and opcodes libraries as shared 70libraries. You can use arguments with the --enable-shared option to 71indicate that only certain libraries should be built shared; for 72example, --enable-shared=bfd. The only potential shared libraries in 73a binutils release are bfd and opcodes. 74 75The binutils will be linked against the shared libraries. The build |
| 65step will attempt to place the correct library in the runtime search | 76step will attempt to place the correct library in the run-time 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 | 77path for the binaries. However, in some cases, after you install the 78binaries, you may have to set an environment variable, normally 79LD_LIBRARY_PATH, so that the system can find the installed libbfd 80shared library. 81 82To build under openVMS/AXP, see the file makefile.vms in the top level 83directory. 84 |
| 85 |
|
| 74If you don't have ar 75==================== 76 | 86If you don't have ar 87==================== 88 |
| 77If your system does not already have an ar program, the normal | 89If 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_PROG="${MAKE-make}" 83MAKE="${MAKE_PROG} AR=true LINK=true" 84export MAKE 85${MAKE} $* all-libiberty --- 7 unchanged lines hidden (view full) --- 93This script will build an ar program in binutils/ar. Move binutils/ar 94into a directory on your PATH. After doing this, you can run make as 95usual to build the complete binutils distribution. You do not need 96the ranlib program in order to build the distribution. 97 98Porting 99======= 100 | 90binutils build process will not work. In this case, run configure as 91usual. Before running make, run this script: 92 93#!/bin/sh 94MAKE_PROG="${MAKE-make}" 95MAKE="${MAKE_PROG} AR=true LINK=true" 96export MAKE 97${MAKE} $* all-libiberty --- 7 unchanged lines hidden (view full) --- 105This script will build an ar program in binutils/ar. Move binutils/ar 106into a directory on your PATH. After doing this, you can run make as 107usual to build the complete binutils distribution. You do not need 108the ranlib program in order to build the distribution. 109 110Porting 111======= 112 |
| 101Binutils-2.9 supports many different architectures, but there | 113Binutils-2.11 supports many different architectures, but there |
| 102are many more not supported, including some that were supported | 114are many more not supported, including some that were supported |
| 103by earlier versions. We are hoping for volunteers to 104improve this situation. | 115by earlier versions. We are hoping for volunteers to improve this 116situation. |
| 105 106The major effort in porting binutils to a new host and/or target 107architecture involves the BFD library. There is some documentation 108in ../bfd/doc. The file ../gdb/doc/gdbint.texinfo (distributed 109with gdb-4.x) may also be of help. 110 111Reporting bugs 112============== 113 | 117 118The major effort in porting binutils to a new host and/or target 119architecture involves the BFD library. There is some documentation 120in ../bfd/doc. The file ../gdb/doc/gdbint.texinfo (distributed 121with gdb-4.x) may also be of help. 122 123Reporting bugs 124============== 125 |
| 114Send bug reports and patches to bug-binutils@gnu.org. Always mention 115the version number you are running; this is printed by running any of 116the binutils with the --version option. We appreciate reports about 117bugs, but we do not promise to fix them. | 126Send bug reports and patches to: |
| 118 | 127 |
| 128 bug-binutils@gnu.org. 129 130Always mention the version number you are running; this is printed by 131running any of the binutils with the --version option. We appreciate 132reports about bugs, but we do not promise to fix them. 133 |
|
| 119VMS 120=== 121 122This section was written by Klaus K"ampf <kkaempf@rmi.de>. It 123describes how to build and install the binutils on openVMS (Alpha and 124Vax). (The BFD library only supports reading Vax object files.) 125 126Compiling the release: --- 24 unchanged lines hidden (view full) --- 151 152On the Alpha you can choose the compiler by editing the toplevel 153makefile.vms. Either select CC=cc (for DEC C) or CC=gcc (for GNU C) 154 155 156Installing the release 157 158Provided that your directory setup conforms to the GNU on openVMS | 134VMS 135=== 136 137This section was written by Klaus K"ampf <kkaempf@rmi.de>. It 138describes how to build and install the binutils on openVMS (Alpha and 139Vax). (The BFD library only supports reading Vax object files.) 140 141Compiling the release: --- 24 unchanged lines hidden (view full) --- 166 167On the Alpha you can choose the compiler by editing the toplevel 168makefile.vms. Either select CC=cc (for DEC C) or CC=gcc (for GNU C) 169 170 171Installing the release 172 173Provided that your directory setup conforms to the GNU on openVMS |
| 159standard, you already have a concealed deviced named 'GNU_ROOT'. | 174standard, you already have a concealed device named 'GNU_ROOT'. |
| 160In this case, a simple 161 162 $ gmake install 163 164suffices to copy all programs and libraries to the proper directories. 165 166Define the programs as foreign commands by adding these lines to your 167login.com: --- 6 unchanged lines hidden (view full) --- 174 175If you have a different directory setup, copy the binary utilities 176([.binutils]size.exe, [.binutils]nm.exe, [.binutils]objdump.exe, 177and [.binutils]strings.exe) and the gnu assembler and preprocessor 178([.gas]as.exe and [.gas]gasp.exe]) to a directory of your choice 179and define all programs as foreign commands. 180 181 | 175In this case, a simple 176 177 $ gmake install 178 179suffices to copy all programs and libraries to the proper directories. 180 181Define the programs as foreign commands by adding these lines to your 182login.com: --- 6 unchanged lines hidden (view full) --- 189 190If you have a different directory setup, copy the binary utilities 191([.binutils]size.exe, [.binutils]nm.exe, [.binutils]objdump.exe, 192and [.binutils]strings.exe) and the gnu assembler and preprocessor 193([.gas]as.exe and [.gas]gasp.exe]) to a directory of your choice 194and define all programs as foreign commands. 195 196 |
| 182If you're satiesfied with the compilation, you may want to remove | 197If you're satisfied with the compilation, you may want to remove |
| 183unneeded objects and libraries: 184 185 $ gmake clean 186 187 188If you have any problems or questions about the binutils on VMS, feel 189free to mail me at kkaempf@rmi.de. | 198unneeded objects and libraries: 199 200 $ gmake clean 201 202 203If you have any problems or questions about the binutils on VMS, feel 204free to mail me at kkaempf@rmi.de. |