Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>,
	Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: [ANNOUNCEMENT] GDB BuildBot
Date: Fri, 23 Jan 2015 10:14:00 -0000	[thread overview]
Message-ID: <54C21AC9.7000109@redhat.com> (raw)
In-Reply-To: <83ppa5uaqj.fsf@gnu.org>

On 01/23/2015 09:06 AM, Eli Zaretskii wrote:
>> From: Sergio Durigan Junior <sergiodj@redhat.com>

>> If the "make TAGS" step proves to be too difficult to implement in the
>> regular build process, I will create a special builder just for it.
> 
> I don't think we need to go that far.  Simply adding "cd $(srcdir) &&"
> to the TAGS rules that don't already do that should be good enough.

Yes, we should do that.  It's what we do to other similar rules
that  generate files in the source dir, like e.g.,

$(srcdir)/aclocal.m4: @MAINTAINER_MODE_TRUE@ $(aclocal_m4_deps)
	cd $(srcdir) && $(ACLOCAL) $(ACLOCAL_AMFLAGS)

> Alternatively, you could do just "make -C gdb TAGS".

Agreed, though I'd say "in addition", rather than "alternatively".  It's
still good to make it easy to generate TAGS without having to reconfigure.

> After all, we
> don't necessarily need to fix the entire repository, only the parts
> that are under our responsibility.  Perhaps this is the best
> alternative, on balance.

Thanks,
Pedro Alves


  reply	other threads:[~2015-01-23  9:57 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
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 [this message]
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=54C21AC9.7000109@redhat.com \
    --to=palves@redhat.com \
    --cc=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