all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: etags bug?
Date: Mon, 25 Dec 2006 21:25:43 -0500	[thread overview]
Message-ID: <E1Gz20d-0003eI-19@fencepost.gnu.org> (raw)

Is this a bug in etags, or in Emacs, or are these #line directives
in Linux incorrect?

If it is a bug in etags, would you please fix this ASAP?
If it is a bug in tags.el, could you tell us what is going on?

------- Start of forwarded message -------
From: Don Mullis <dwm@meer.net>
To: kbuild-devel@lists.sourceforge.net, emacs-devel@gnu.org
Content-Type: text/plain
Date: Sun, 24 Dec 2006 12:01:31 -0800
Mime-Version: 1.0
Cc: kai@germaschewski.name, sam@ravnborg.org
Subject: [PATCH, RFC] etags/ctags v22.0.92 break Linux kernel `make
	TAGS/tags`
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed 
	version=3.0.4

`make TAGS` produces a TAGS that causes the emacs v22.0.92 command 
'M-x tags-search' to repeatedly stop with complaints about missing files.
Proximate cause of this is "#line" directives in Linux source files.

`make tags` produces hundreds of lines of complaints about duplicate
entries.

The following ugly patch works around these problems.  Posting to
both kbuild-devel and emacs-devel in hopes something better can be worked out
for the Emacs v22 release.

- ---
 Makefile |   12 ++++++++++++
 1 file changed, 12 insertions(+)

Index: linux-2.6/Makefile
===================================================================
- --- linux-2.6.orig/Makefile
+++ linux-2.6/Makefile
@@ -1337,6 +1337,18 @@ define xtags
 		--langdef=dotconfig \
 		--language-force=dotconfig \
 		--regex-dotconfig='/^#?[[:blank:]]*(CONFIG_[[:alnum:]_]+)/\1/'; \
+	elif $1 --version 2>&1 | grep -iq 'ctags.* 22\.'; then \
+	    $(all-sources) | xargs $1 -a -w; \
+	    $(all-kconfigs) | xargs $1 -a -w \
+		--regex='/^[ \t]*config[ \t]+\([a-zA-Z0-9_]+\)/\1/'; \
+	    $(all-defconfigs) | xargs -r $1 -a -w \
+		--regex='/^#?[ \t]?\(CONFIG_[a-zA-Z0-9_]+\)/\1/'; \
+	elif $1 --version 2>&1 | grep -iq 'etags.* 22\.'; then \
+	    $(all-sources) | xargs $1 -a --no-line-directive; \
+	    $(all-kconfigs) | xargs $1 -a --no-line-directive \
+		--regex='/^[ \t]*config[ \t]+\([a-zA-Z0-9_]+\)/\1/'; \
+	    $(all-defconfigs) | xargs -r $1 -a --no-line-directive \
+		--regex='/^#?[ \t]?\(CONFIG_[a-zA-Z0-9_]+\)/\1/'; \
 	elif $1 --version 2>&1 | grep -iq emacs; then \
 	    $(all-sources) | xargs $1 -a; \
 	    $(all-kconfigs) | xargs $1 -a \




_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
------- End of forwarded message -------

                 reply	other threads:[~2006-12-26  2:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1Gz20d-0003eI-19@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.