From: Eli Zaretskii <eliz@gnu.org>
To: sergiodj@redhat.com
Cc: gdb@sourceware.org
Subject: Re: [ANNOUNCEMENT] GDB BuildBot
Date: Thu, 22 Jan 2015 21:32:00 -0000 [thread overview]
Message-ID: <83sif2tucs.fsf@gnu.org> (raw)
In-Reply-To: <83twzitur9.fsf@gnu.org>
> Date: Thu, 22 Jan 2015 22:39:38 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: gdb@sourceware.org
>
> > TAGS: $(CFILES)
> > etags `for i in $(CFILES); do echo $(srcdir)/$$i ; done`
> >
> > and CFILES is just a list of files, without $(srcdir)/. So this can
> > only work when building inside the source tree.
>
> On second thought, TAGS files _should_ be in the source tree, because
> that's where they will be used.
>
> So how about running "make TAGS" in the source tree? Can this be
> done in the BuildBot?
And btw, why doesn't VPATH work in this case?
next prev parent reply other threads:[~2015-01-22 20:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 23:43 Sergio Durigan Junior
2015-01-15 12:13 ` Joel Brobecker
2015-01-15 19:36 ` Sergio Durigan Junior
2015-01-21 22:53 ` Sergio Durigan Junior
2015-01-22 18:15 ` Eli Zaretskii
2015-01-22 18:38 ` Sergio Durigan Junior
2015-01-22 18:43 ` Eli Zaretskii
2015-01-22 18:57 ` Sergio Durigan Junior
2015-01-22 19:25 ` Eli Zaretskii
2015-01-22 19:55 ` Eli Zaretskii
2015-01-22 20:32 ` Sergio Durigan Junior
2015-01-22 20:39 ` Eli Zaretskii
2015-01-22 20:48 ` Eli Zaretskii
2015-01-22 21:32 ` Eli Zaretskii [this message]
2015-01-22 22:28 ` Sergio Durigan Junior
2015-01-22 22:34 ` Doug Evans
2015-01-23 9:06 ` Sergio Durigan Junior
2015-01-23 9:57 ` Eli Zaretskii
2015-01-23 9:09 ` Eli Zaretskii
2015-01-23 10:14 ` Pedro Alves
2015-01-23 11:01 ` Eli Zaretskii
2015-01-23 16:16 ` Andreas Schwab
2015-01-23 17:47 ` Eli Zaretskii
2015-01-22 21:46 ` Sergio Durigan Junior
2015-01-23 10:41 ` Pedro Alves
2015-01-23 10:46 ` Eli Zaretskii
2015-01-23 14:25 ` Pedro Alves
2015-01-27 16:42 ` Mark Wielaard
2015-01-27 20:05 ` Sergio Durigan Junior
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=83sif2tucs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=sergiodj@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).