Re: Building GDB 7.3.92 with MinGW

Alfred M. Szmidt
2012-01-10T19:25:34Z

2. "make install-strip" fails in readline/, in sim/, and in gdb/:

make[2]: Entering directory `/d/usr/eli/utils/gdb-7.3.92/readline'
make[2]: *** No rule to make target `install-strip'. Stop.
make[2]: Leaving directory `/d/usr/eli/utils/gdb-7.3.92/readline'
make[1]: *** [install-strip-readline] Error 2
make[2]: Entering directory `/d/usr/eli/utils/gdb-7.3.92/sim'
make[2]: *** No rule to make target `install-strip'.
make[2]: Leaving directory `/d/usr/eli/utils/gdb-7.3.92/sim'
make[1]: *** [install-strip-sim] Error 2
make[2]: Entering directory `/d/usr/eli/utils/gdb-7.3.92/gdb'
make[2]: *** No rule to make target `install-strip'.
make[2]: Leaving directory `/d/usr/eli/utils/gdb-7.3.92/gdb'
make[1]: *** [install-strip-gdb] Error 2
make[1]: Target `install-strip-host' not remade because of errors.
make[1]: Nothing to be done for `install-strip-target'.
make[1]: Leaving directory `/d/usr/eli/utils/gdb-7.3.92'
make: *** [install-strip] Error 2

The reason is that these directories simply don't have the
"install-strip" target in their Makefile.in files. I think that
target should be added, because that's AFAIK how GDB is supposed
to be installed on end-user systems.

`make install' is generally the way one should install GNU projects on
a end-user system, since that makes it possible to debug things (hence
why CFLAGS contains -g by default); install-strip is really for people
with little disk space.

Finally, a question: Why are we installing libraries (libbfd,
libopcodes, libiberty) and the standards.info manual? The
libraries are not part of GDB, we import them from elsewhere.
"make install" will happily overwrite existing installation of
these libraries that could potentially be newer, coming from their
respective upstream distributions. How about removing these from
"make install"?

I personally never understood why they get installed by binutils, or
gdb.