Re: gdb.c++ vs dos names

Michael Elizabeth Chastain
2003-01-09T20:49:27Z

It seems to work for me. 'make -f src-release gdb.tar' gives
me a tarball with no testsuite/gdb.*/Makefile in it.

Two directories still have both a 'Makefile' and 'Makefile.in'
in the tarball:

% tar tf gdb.tar | grep Makefile
...
utils/sparclite/Makefile.in
utils/sparclite/Makefile
...
utils/wince/Makefile.in
utils/wince/Makefile
...

utils/configure.in does not use AC_OUTPUT so there is some other glitch.
This is probably a bug as the generated Makefile has had all its
variables substituted by the release process.

config/djgpp/fnchange.lst is still missing some legitimate files
in gdb.c++. I will submit a patch for that shortly.

Michael C

===

2003-01-09 Daniel Jacobowitz <drow@mvista.com>

* Makefile.in (ALL_SUBDIRS): New variable.
(subdirs, clean, distclean): Use it.
* gdb.arch/Makefile.in: Clean up Makefile. Remove rules for
regenerating Makefile, since it is generated from the top level.
* gdb.asm/Makefile.in: Likewise.
* gdb.base/Makefile.in: Likewise.
* gdb.c++/Makefile.in: Likewise.
* gdb.disasm/Makefile.in: Likewise.
* gdb.java/Makefile.in: Likewise.
* gdb.mi/Makefile.in: Likewise.
* gdb.threads/Makefile.in: Likewise.
* gdb.trace/Makefile.in: Likewise.