Next: Versions and Branches, Previous: Coding, Up: Top
Most of the work in making gdb compile on a new machine is in
specifying the configuration of the machine. This is done in a
dizzying variety of header files and configuration scripts, which we
hope to make more sensible soon. Let's say your new host is called an
xyz (e.g., `sun4'), and its full three-part configuration
name is arch-
xvend-
xos (e.g.,
`sparc-sun-sunos4'). In particular:
-
xvend-
xos. You can test your changes by
running
./config.sub xyz
and
./config.sub arch-
xvend-
xos
which should both respond with arch-
xvend-
xos
and no error messages.
You need to port BFD, if that hasn't been done already. Porting BFD is beyond the scope of this manual.
gdb_host
to xyz, and (unless your
desired target is already available) also edit gdb/configure.tgt,
setting gdb_target
to something appropriate (for instance,
xyz).
Maintainer's note: Work in progress. The file gdb/configure.host originally needed to be modified when either a new native target or a new host machine was being added to gdb. Recent changes have removed this requirement. The file now only needs to be modified when adding a new native configuration. This will likely changed again in the future.