From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Tom Tromey'" <tromey@redhat.com>, <gdb-patches@sourceware.org>
Subject: RE: add TAGS target in testsuite
Date: Mon, 07 Mar 2011 18:00:00 -0000 [thread overview]
Message-ID: <000001cbdcec$04815b10$0d841130$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <m3vczun9qt.fsf@fleche.redhat.com>
I wanted to try this out, but
I got this:
Pierre@E6510-Muller ~/gdbcvs/build-norm/gdb/testsuite
$ etags --version
Exuberant Ctags 5.8, Copyright (C) 1996-2009 Darren Hiebert
Compiled: Dec 11 2009, 11:42:40
Addresses: <dhiebert@users.sourceforge.net>, http://ctags.sourceforge.net
Optional compiled features: +wildcards, +regex, +internal-sort
Pierre@E6510-Muller ~/gdbcvs/build-norm/gdb/testsuite
$ make TAGS
etags --language=none --regex='/proc[ \t]+\([^ \t]+\)/\1/' \
`find ../../../src/gdb/testsuite -name '*.exp' -print`
etags: Warning: "--language" option is obsolete; use "--language-force"
instead
etags: Unknown language "none" in "language" option
make: *** [TAGS] Error 1
Pierre
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Tom Tromey
> Envoyé : lundi 7 mars 2011 18:04
> À : gdb-patches@sourceware.org
> Objet : FYI: add TAGS target in testsuite
>
> I am checking this in.
>
> I wanted to be able to use tags in the testsuite. This patch adds a
> "TAGS" target to the testsuite Makefile.
>
> I am undecided as to whether I should add this to gdb/TAGS via `etags
> --include'. If you use etags, and have an opinion, let me know.
>
> Tom
>
> 2011-03-07 Tom Tromey <tromey@redhat.com>
>
> * Makefile.in (TAGS): New target.
>
> diff --git a/gdb/testsuite/Makefile.in b/gdb/testsuite/Makefile.in
> index c1356c5..8017ff0 100644
> --- a/gdb/testsuite/Makefile.in
> +++ b/gdb/testsuite/Makefile.in
> @@ -242,3 +242,7 @@ Makefile : Makefile.in config.status
> $(host_makefile_frag)
>
> config.status: configure
> $(SHELL) config.status --recheck
> +
> +TAGS: force
> + etags --language=none --regex='/proc[ \t]+\([^ \t]+\)/\1/' \
> + `find $(srcdir) -name '*.exp' -print`
next prev parent reply other threads:[~2011-03-07 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 17:24 FYI: " Tom Tromey
2011-03-07 18:00 ` Pierre Muller [this message]
[not found] ` <21165.0532474325$1299518488@news.gmane.org>
2011-03-07 18:06 ` Tom Tromey
2011-03-07 18:42 ` Eli Zaretskii
2011-03-08 1:11 ` Tom Tromey
2011-03-07 18:43 ` FYI: " Eli Zaretskii
2011-03-07 20:10 ` Michael Snyder
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='000001cbdcec$04815b10$0d841130$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox