public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Remove REMOTE_EXAMPLES from gdb/Makefile.in
Date: Mon, 27 Jul 2015 16:26:00 -0000	[thread overview]
Message-ID: <206350da0f99b9a50fe6405613b3b05561a55aae@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 206350da0f99b9a50fe6405613b3b05561a55aae ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 206350da0f99b9a50fe6405613b3b05561a55aae

Remove REMOTE_EXAMPLES from gdb/Makefile.in
I happen to see REMOTE_EXAMPLES isn't used anywhere, so this patch
removes it.

REMOTE_EXAMPLES was added in the following commit in 1991,

commit 86bbb439c8fa01fd55d6cbce102483a471ffd0c4
Author: John Gilmore <gnu@cygnus>
Date:   Fri May 3 19:57:13 1991 +0000

    There should be a Makefile in the cvs main directory, configured
    for "./config.gdb none", so that things like "make tags" and "make tar"
    will work.

and it was used like:

TARFILES = ${TAGFILES_MAINDIR} ${OTHERS} ${REMOTE_EXAMPLES}

However TARFILES was removed by the change latter in 1994,

Tue Aug 16 15:24:03 1994  Jim Kingdon  (kingdon@lioth.cygnus.com)

	* symtab.c (decode_line_1): If funfirstline and we get a
	non-LOC_BLOCK symbol (e.g. variable or type), then error().

	* Makefile.in (TARFILES, NONSRC, SFILES_STAND, SFILES_KGDB):
	Remove; unused.

Since then, REMOTE_EXAMPLES is not used any more.

gdb:

2015-07-27  Yao Qi  <yao.qi@linaro.org>

	* Makefile.in (REMOTE_EXAMPLES): Remove it.


             reply	other threads:[~2015-07-27 16:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 16:26 sergiodj+buildbot [this message]
2015-07-27 16:26 ` Failures on AIX-POWER7-plain, branch master sergiodj+buildbot
2015-07-27 16:46 ` Failures on Fedora-i686, " sergiodj+buildbot
2015-07-27 16:58 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2015-07-27 17:02 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2015-07-27 17:04 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2015-07-27 17:05 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-07-27 18:20 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2015-07-27 19:17 ` Failures on Debian-i686, " sergiodj+buildbot
2015-07-27 19:29 ` Failures on Debian-MIPS-m64, " sergiodj+buildbot
2015-07-27 19:34 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2015-07-27 19:58 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2015-07-27 20:58 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2015-07-29  4:06 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2015-07-29  4:22 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2015-07-29  4:43 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-07-29 14:25 ` Failures on Fedora-ppc64le-native-extended-gdbserver-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=206350da0f99b9a50fe6405613b3b05561a55aae@gdb-build \
    --to=sergiodj+buildbot@redhat.com \
    --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).