3 --> FILE LOCATIONS IN THE ORIGINAL TAR FILE:
4 - config.h and reg-mips.c file are generated by the configure application (see below)
6 - regdef.h: /gdb/regformats/
8 gdb_proc_service.h: /gdb/
9 /gdb/signals.h: /include/gdb/
11 - Makefile is Broadcom proprietary file.
13 - All other files are from /gdb/gdbserver directory except /gdb/signals.h, which is in
14 /include/gdb/ directory of the tar file.
17 --> GENERATING CONFIG.H AND REG-MIPS.C FILES FROM THE TAR FILE:
18 - Untar the source tar file. For example if the tar file is insight-6.1.tar.gz, then use:
19 tar xvzf insight-6.1.tar.gz.
20 This will create a directory insight-6.1
22 - Make a directory for the gdbserver and call it insight-6.1-mips in the place where the sources
23 were untarred. So if the files were untarred in ~/insight then create this directory as
27 - Change to the new directory: cd insight-6.1-mips
29 - Export some variables using
30 export CC=/opt/toochains/uclibc/bin/mips-uclibc-gcc
31 export LDFLAGS=-static
33 - Make the configuration file executable: chmod +x ../insight-6.1/gdb/gdbserver/configure
35 - Run the configure program to export some more variables:
36 ../insight-6.1/gdb/gdbserver/configure --target=mips-linux
38 This procedure should have created config.h and reg-mips.c files in insight-6.1-mips directory.