There's an etags target in the build/Makefile:
etags tags: TAGS
However, when invoking this target, I get:
make etags
make[1]: Entering directory `/home/evansl/download/gcc/4.4-20090630/build'
Doing TAGS in gcc
make[2]: Entering directory `/home/evansl/download/gcc/4.4-20090630/build/gcc'
cd /home/evansl/download/gcc/4.4-20090630/build/../src/gcc/cp; etags -o
TAGS.sub *.c *.h --language=none \
--regex='/DEFTREECODE [(]\([A-Z_]+\)/\1/' cp-tree.def; \
etags --include TAGS.sub --include ../TAGS.sub
etags: Warning: "--language" option is obsolete; use "--language-force" instead
etags: Unknown language "none" in "language" option
etags: Unknown option: --include
make[2]: *** [c++.tags] Error 1
make[2]: Leaving directory `/home/evansl/download/gcc/4.4-20090630/build/gcc'
make[1]: *** [TAGS-gcc] Error 1
make[1]: Leaving directory `/home/evansl/download/gcc/4.4-20090630/build'
make: *** [do-TAGS] Error 2
This does produce a TAGS.sub in the cp directory, but nowhere else,
AFAICT:
-*- mode: compilation; default-directory: "~/download/gcc/4.4-20090630/src/" -*-
Compilation started at Thu Jul 23 07:21:32
find . -name TAGS.sub -ls
5985718 256 -rw-r--r-- 1 evansl evansl 257692 Jul 23 07:12
./gcc/cp/TAGS.sub
What changes will avoid etags error message about unknown language and
how do I get the TAGS.sub for the gcc directory?
Oh, and BTW, does anyone find etags useful? I thought it would be useful
since often I find myself using grep to find where a function or marco
is defined and I thought *maybe* using emacs' etags feature would be
useful; however, I've no experience with it.
TIA.
-Larry
