public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Automatically update "aclocal_m4_deps" when updating gnulib
Date: Wed, 05 Sep 2018 22:50:00 -0000	[thread overview]
Message-ID: <fcc9b044b7f563023633a9964810e76f4cde40d4@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT fcc9b044b7f563023633a9964810e76f4cde40d4 ***

Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: fcc9b044b7f563023633a9964810e76f4cde40d4

Automatically update "aclocal_m4_deps" when updating gnulib

When we update gnulib using our "update-gnulib.sh" tool, it doesn't
automatically update the list of M4 files present at
gnulib/Makefile.in:aclocal_m4_deps.  This patch extends the tool to do
that.  It also puts "aclocal_m4_deps" in its own file (a Makefile
fragment), so that it's easier to update it programatically.

Tested by generating the file and diff'ing the results against the
current version of "aclocal_m4_deps".

gdb/ChangeLog:
2018-09-04  Sergio Durigan Junior  <sergiodj@redhat.com>
	    Pedro Alves  <palves@redhat.com>

	* gnulib/Makefile.in (aclocal_m4_deps): Move to
	"aclocal-m4-deps.mk".  Include file here.
	$(srcdir)/aclocal.m4: Add "configure.ac".
	* gnulib/aclocal-m4-deps.mk: New file.
	* gnulib/update-gnulib.sh: Automatically update
	"aclocal-m4-deps.mk".


             reply	other threads:[~2018-09-04 18:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-05 22:50 sergiodj+buildbot [this message]
2018-09-05 22:14 ` *** COMPILATION FAILED *** Failures on Debian-s390x-native-extended-gdbserver-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2018-09-05 23:25 ` *** COMPILATION FAILED *** Failures on RHEL-s390x-m64, " sergiodj+buildbot
2018-09-05 23:32 ` *** COMPILATION FAILED *** Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-09-05 23:32 ` *** COMPILATION FAILED *** Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-09-06 10:54 ` Failures on Fedora-x86_64-cc-with-index, branch master sergiodj+buildbot
2018-09-06 11:00 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-09-06 11:14 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-09-06 11:14 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-09-06 11:16 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-09-10 20:58 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot

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=fcc9b044b7f563023633a9964810e76f4cde40d4@gdb-build \
    --to=sergiodj+buildbot@sergiodj.net \
    --cc=gdb-testers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).