GDB comes with a configure script that automates the process
of preparing GDB for installation; you can then use
The GDB distribution includes all the source code you need for GDB in a single directory, whose name is usually composed by appending the version number to ‘gdb’.
For example, the GDB version 184.108.40.20681219-git distribution is in the gdb-220.127.116.1181219-git directory. That directory contains:
gdb-18.104.22.16881219-git/configure (and supporting files)
script for configuring GDB and all its supporting libraries
the source specific to GDB itself
source for the Binary File Descriptor library
GNU include files
source for the ‘-liberty’ free software library
source for the library of opcode tables and disassemblers
source for the GNU command-line interface
There may be other subdirectories as well.
The simplest way to configure and build GDB is to run configure from the gdb-version-number source directory, which in this example is the gdb-22.214.171.12481219-git directory.
First switch to the gdb-version-number source directory if you are not already in it; then run configure. Pass the identifier for the platform on which GDB will run as an argument.
cd gdb-126.96.36.19981219-git ./configure make
Running ‘configure’ and then running
make builds the
included supporting libraries, then
gdb itself. The configured
source files, and the binaries, are left in the corresponding source
configure is a Bourne-shell (
/bin/sh) script; if your
system does not recognize this automatically when you run a different
shell, you may need to run
sh on it explicitly:
You should run the configure script from the top directory in the source tree, the gdb-version-number directory. If you run configure from one of the subdirectories, you will configure only that subdirectory. That is usually not what you want. In particular, if you run the first configure from the gdb subdirectory of the gdb-version-number directory, you will omit the configuration of bfd, readline, and other sibling directories of the gdb subdirectory. This leads to build errors about missing include files such as bfd/bfd.h.
You can install
GDB anywhere. The best way to do this
is to pass the
--prefix option to
configure, and then
install it with