Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: [ANNOUNCEMENT] GDB BuildBot
Date: Thu, 22 Jan 2015 22:28:00 -0000	[thread overview]
Message-ID: <87sif25vzr.fsf@redhat.com> (raw)
In-Reply-To: <83sif2tucs.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 22 Jan	2015 22:48:19 +0200")

On Thursday, January 22 2015, Eli Zaretskii wrote:

>> 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?

On a second thought (from my side), I would have to run configure from
the srcdir before "make TAGS"...  While I can do that, I'm trying to
avoid having too many unecessary steps in the build.

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.

-- 
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


  reply	other threads:[~2015-01-22 21:46 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 [this message]
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=87sif25vzr.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox