From: Eli Zaretskii <eliz@gnu.org>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: [ANNOUNCEMENT] GDB BuildBot
Date: Thu, 22 Jan 2015 19:55:00 -0000 [thread overview]
Message-ID: <83y4outyxl.fsf@gnu.org> (raw)
Message-ID: <20150122195500.to7d5jsONzjFCLI2wIAqy8JofP5dZmCvqp4Gwhug2Oc@z> (raw)
In-Reply-To: <87mw5a8x34.fsf@redhat.com>
> From: Sergio Durigan Junior <sergiodj@redhat.com>
> Cc: gdb@sourceware.org
> Date: Thu, 22 Jan 2015 13:54:55 -0500
>
> >> > Did my recent commit fix this at least for some targets?
> >>
> >> No, all builders are still failing.
> >
> > Because of libdecnumber?
>
> <http://gdb-build.sergiodj.net/builders/Fedora-i686/builds/46/steps/make%20tags/logs/stdio>
>
> Yes.
Thanks, I tried to fix that in this commit:
commit 53bef1c10759f1fd7faf675459871b2f4cc12e53
Author: Eli Zaretskii <eliz@gnu.org>
Date: Thu Jan 22 21:07:31 2015 +0200
Another part of fixing "make TAGS".
libdecnumber/
2015-01-22 Eli Zaretskii <eliz@gnu.org>
* Makefile.in (TAGS): New target, to avoid failures in "make TAGS".
diff --git a/libdecnumber/ChangeLog b/libdecnumber/ChangeLog
index 65d20fc..ec6ea1a 100644
--- a/libdecnumber/ChangeLog
+++ b/libdecnumber/ChangeLog
@@ -1,3 +1,7 @@
+2015-01-22 Eli Zaretskii <eliz@gnu.org>
+
+ * Makefile.in (TAGS): New target, to avoid failures in "make TAGS".
+
2014-01-23 Marek Polacek <polacek@redhat.com>
PR c/59871
diff --git a/libdecnumber/Makefile.in b/libdecnumber/Makefile.in
index b6f3842..8dbada9 100644
--- a/libdecnumber/Makefile.in
+++ b/libdecnumber/Makefile.in
@@ -167,6 +167,8 @@ maintainer-clean: distclean
@echo "it deletes files that may require special tools to rebuild."
-rm -f $(srcdir)/configure $(srcdir)/aclocal.m4
+TAGS:
+
check:
installcheck:
dvi:
next prev parent reply other threads:[~2015-01-22 19:25 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 [this message]
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
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=83y4outyxl.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