None of them is referenced by the Makefile, the release targets or the
documentation:
- gdb_files only echoed ${GDB_FILES} ${GDB_PATCH_FILES}, which is empty
apart from the patch file now that gdb ships as a tarball; "make files"
already prints the complete tarball file list
- glink linked ${GDB}/gdb into the crash root, but crash's gdb patch
redirects gdb's link output to ../../crash, so there is no gdb binary
for it to reach
- name only echoed ${PROGRAM}
- ref only ran "make ctags cscope"
The embedded gdb's files and patch file remain in the "make files" output,
because show_files prints ${GDB_FILES} ${GDB_PATCH_FILES} itself.
Assisted-by: LLM
Signed-off-by: Dave Young <yangrr.2009(a)tsinghua.org.cn>
---
Makefile | 22 ++++++----------------
1 file changed, 6 insertions(+), 16 deletions(-)
diff --git a/Makefile b/Makefile
index 46c43a42dbae..c392c23b7327 100644
--- a/Makefile
+++ b/Makefile
@@ -622,10 +622,12 @@ files: make_configure
@./configure -q -b
@$(MAKE) show_files
-gdb_files: make_configure
- @./configure -q -b
- @echo ${GDB_FILES} ${GDB_PATCH_FILES}
-
+#
+# The list of files which make up a release tarball. The embedded gdb's
+# files and its patch file(s) are included through GDB_FILES and
+# GDB_PATCH_FILES, which is why "make files" still lists them even though
+# there is no separate gdb_files target.
+#
show_files:
@if [ -f ${PROGRAM} ]; then \
./${PROGRAM} --no_scroll --no_crashrc -h README > README; fi
@@ -701,24 +703,12 @@ do_release:
ls -l ${PROGRAM}-${VERSION}-${RELEASE}.src.rpm; \
fi
-ref:
- $(MAKE) ctags cscope
-
cscope:
rm -f cscope.files cscope.out
for FILE in ${SOURCE_FILES}; do \
echo $$FILE >> cscope.files; done
cscope -b -f cscope.out
-glink: make_configure
- @./configure -q -b
- rm -f gdb
- ln -s ${GDB}/gdb gdb
- (cd ${GDB}/gdb; rm -f ${PROGRAM}; ln -s ../../${PROGRAM} ${PROGRAM})
-
-name:
- @echo ${PROGRAM}
-
dis:
objdump --disassemble --line-numbers ${PROGRAM} > ${PROGRAM}.dis
--
2.51.1