%general-entities; ]> binutils &binutils-version;

&binutils-url;

Binutils Verify that the PTYs are working properly inside the chroot environment by performing a simple test: expect -c "spawn ls" This command should output the following: spawn ls If, instead, the output includes the message below, then the environment is not set up for proper PTY operation. This issue needs to be resolved before running the test suites for Binutils and GCC: The system has no more ptys. Ask your system administrator to create more. The Binutils documentation recommends building Binutils in a dedicated build directory: mkdir -v build cd build Prepare Binutils for compilation: ../configure --prefix=/usr \ --enable-shared \ --enable-plugins \ --disable-werror \ --with-system-zlib --enable-plugins Enables plugin support for the linker. --with-system-zlib Use the installed zlib library rather than building the included version. Compile the package: make tooldir=/usr tooldir=/usr Normally, the tooldir (the directory where the executables will ultimately be located) is set to $(exec_prefix)/$(target_alias). For example, x86_64 machines would expand that to /usr/x86_64-unknown-linux-gnu. Because this is a custom system, this target-specific directory in /usr is not required. $(exec_prefix)/$(target_alias) would be used if the system was used to cross-compile (for example, compiling a package on an Intel machine that generates code that can be executed on PowerPC machines). The test suite for Binutils in this section is considered critical. Do not skip it under any circumstances. Test the results: make -k check Install the package: make tooldir=/usr install Installed programs Installed libraries Installed directory addr2line, ar, as, c++filt, elfedit, gprof, ld, ld.bfd, nm, objcopy, objdump, ranlib, readelf, size, strings, and strip libbfd.{a,so} and libopcodes.{a,so} /usr/lib/ldscripts Short Descriptions addr2line Translates program addresses to file names and line numbers; given an address and the name of an executable, it uses the debugging information in the executable to determine which source file and line number are associated with the address addr2line ar Creates, modifies, and extracts from archives ar as An assembler that assembles the output of gcc into object files as c++filt Used by the linker to de-mangle C++ and Java symbols and to keep overloaded functions from clashing c++filt elfedit Updates the ELF header of ELF files elfedit gprof Displays call graph profile data gprof ld A linker that combines a number of object and archive files into a single file, relocating their data and tying up symbol references ld ld.bfd Hard link to ld ld.bfd nm Lists the symbols occurring in a given object file nm objcopy Translates one type of object file into another objcopy objdump Displays information about the given object file, with options controlling the particular information to display; the information shown is useful to programmers who are working on the compilation tools objdump ranlib Generates an index of the contents of an archive and stores it in the archive; the index lists all of the symbols defined by archive members that are relocatable object files ranlib readelf Displays information about ELF type binaries readelf size Lists the section sizes and the total size for the given object files size strings Outputs, for each given file, the sequences of printable characters that are of at least the specified length (defaulting to four); for object files, it prints, by default, only the strings from the initializing and loading sections while for other types of files, it scans the entire file strings strip Discards symbols from object files strip libbfd The Binary File Descriptor library libbfd libopcodes A library for dealing with opcodes—the readable text versions of instructions for the processor; it is used for building utilities like objdump libopcodes