aboutsummaryrefslogtreecommitdiff
path: root/gdb/expprint.c
diff options
context:
space:
mode:
authorJoel Brobecker <brobecker@adacore.com>2015-01-13 18:59:32 +0400
committerJoel Brobecker <brobecker@adacore.com>2015-01-13 19:24:54 +0400
commit576fd14c6861ef937a50b5a7500c8a58f8c4ea92 (patch)
treeac3c282a582bc7237afbb581f713f5f6b7854cea /gdb/expprint.c
parent3b2f13ff2f2af1688c179c971ade19b8e9989076 (diff)
downloadgdb-576fd14c6861ef937a50b5a7500c8a58f8c4ea92.zip
gdb-576fd14c6861ef937a50b5a7500c8a58f8c4ea92.tar.gz
gdb-576fd14c6861ef937a50b5a7500c8a58f8c4ea92.tar.bz2
gdb/testsuite: Make clean mostlyclean should not delete *.py.
A sanity-check in my release scripts caught something: After having created the tarballs, I verify that no checked-in file disappeared in the process, and lo and behod, it found that the following file got wiped: - gdb/testsuite/dg-extract-results.py: And it's not part of the tarball either. I don't understand while we delete all *.py files in gdb/testsuite, since I don't see a rule that expected to create one. A run of the testsuite also doesn't seem to be creating .py files there. I traced this to the following commit, which unfortunately provided no explanation. Perhaps we used to run some tests in the gdb/testsuite directory and caused files to be left behind there. Perhaps we still do today? In the meantime, Executive Decision: In order to allow me to create tarballs without losing files, I removed it. It's easy to put something back if we find out why it might still be needed. gdb/testsuite/ChangeLog: * Makefile.in (clean mostlyclean): Do not delete *.py. Tested on x86_64-linux by running the src-release.sh script again, and this time, dg-extract-results.py no longer gets wiped.
Diffstat (limited to 'gdb/expprint.c')
0 files changed, 0 insertions, 0 deletions