unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Don Mullis <dwm@meer.net>
Cc: Olaf Dabrunz <od@suse.de>, emacs-devel@gnu.org
Subject: Re: [PATCH, RFC] etags/ctags v22.0.92 break Linux kernel `make TAGS/tags`
Date: Tue, 26 Dec 2006 10:43:17 -0800	[thread overview]
Message-ID: <1167158597.2706.224.camel@localhost.localdomain> (raw)
In-Reply-To: <E1GzD3E-0006S5-MZ@tucano.isti.cnr.it>

On Tue, 2006-12-26 at 15:13 +0100, Francesco Potorti` wrote:
> >`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.
> 
> I cannot reproduce this on a 2.6.18 Linux tree with Emacs 22.0.91.
> 
> By the way, I did not know that 22.0.92 was out.  Would someone please
> tell me where I can download it?

ftp://alpha.gnu.org/gnu/emacs/pretest/emacs-22.0.92.tar.gz  

> Anyway, etags has not changed in that respect since 22.0.91.  Would you
> please detail precisely the steps you followed to trigger the bug?  

The bug only appears if some `make *config` has succeeded.  Try:

	make allnoconfig
	make TAGS

I have verified that the above shows the bug with 2.6.18 Linux.

> And,
> just to be sure, please let me know the output of 
>  strings `which etags` | fgrep revision
        
        $ strings `which etags` | fgrep revision
        @(#) pot revision number is $Revision$

More usefully:

        $ etags --version
        etags (standalone 22.0.92)
        Copyright (C) 2006 Free Software Foundation, Inc. and Ken Arnold
        This program is distributed under the same terms as Emacs

  reply	other threads:[~2006-12-26 18:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-24 20:01 [PATCH, RFC] etags/ctags v22.0.92 break Linux kernel `make TAGS/tags` Don Mullis
2006-12-25  5:41 ` Masatake YAMATO
2006-12-25 16:47   ` Don Mullis
2006-12-25 22:36     ` Francesco Potorti`
2006-12-26 14:13 ` Francesco Potorti`
2006-12-26 18:43   ` Don Mullis [this message]
2006-12-28  0:10     ` Francesco Potorti`
2006-12-28  5:48       ` Don Mullis
2006-12-28 10:21         ` Francesco Potorti`
2006-12-29 22:58         ` Richard Stallman
2006-12-30 20:36           ` Don Mullis
2006-12-31  1:46             ` Richard Stallman
2006-12-27  2:59   ` Richard Stallman
2006-12-30 12:15     ` Francesco Potorti`
2006-12-31  1:45       ` Richard Stallman
2007-01-02 11:41         ` Francesco Potorti`
2007-01-02 14:26           ` Frank Schmitt
2007-01-03  1:24             ` Francesco Potorti`
2007-01-03 12:06               ` Frank Schmitt
2007-01-03 14:33                 ` Frank Schmitt
     [not found]               ` <m38xgk47lc.fsf@mid.gehheimdienst.de>
2007-02-05  8:25                 ` Francesco Potorti`
2007-01-02 21:24           ` Richard Stallman
2007-01-03  0:40             ` Francesco Potorti`
2007-01-02 21:24           ` Eli Zaretskii
2007-01-03  0:42             ` Francesco Potorti`

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=1167158597.2706.224.camel@localhost.localdomain \
    --to=dwm@meer.net \
    --cc=emacs-devel@gnu.org \
    --cc=od@suse.de \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).