Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: [patch/6.1] Gdbserver snapshot fix
Date: Fri, 19 Mar 2004 00:09:00 -0000	[thread overview]
Message-ID: <20040304220200.GA29799@nevyn.them.org> (raw)
Message-ID: <20040319000900.Cdx_59lMxIEm9-2nlK7DMLVbSxqY5_wdzsEOCNB2sdw@z> (raw)

When building from a snapshot tarball for arm-linux, I discovered that an
(incorrect, obviously) config.h had been saved in the tarball.  That's
because I never added it to distclean when I gave gdbserver its own
config.h.  I'm not quite sure why this wasn't a problem last release.

Checked in to HEAD and 6.1.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

2004-03-04  Daniel Jacobowitz  <drow@mvista.com>

	* Makefile.in (distclean): Remove config.h, stamp-h, and config.log.
	Unify with other clean targets.

--- src/gdb/gdbserver/Makefile.in	2004-03-02 11:57:42.000000000 -0500
+++ src/gdb/gdbserver/Makefile.in	2004-03-02 14:34:13.000000000 -0500
@@ -1,5 +1,5 @@
 # Copyright 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
-# 1999, 2000, 2001, 2002 Free Software Foundation, Inc.
+# 1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc.
 
 # This file is part of GDB.
 
@@ -200,12 +200,8 @@
 	rm -f reg-arm.c reg-i386.c reg-ia64.c reg-m68k.c reg-mips.c
 	rm -f reg-ppc.c reg-sh.c reg-x86-64.c reg-i386-linux.c
 
-distclean: clean
-	rm -f nm.h tm.h xm.h config.status
-	rm -f Makefile
-
-maintainer-clean realclean: clean
-	rm -f nm.h tm.h xm.h config.status
+maintainer-clean realclean distclean: clean
+	rm -f nm.h tm.h xm.h config.status config.h stamp-h config.log
 	rm -f Makefile
 
 STAGESTUFF=${OBS} ${TSOBS} ${NTSOBS} ${ADD_FILES} init.c init.o version.c gdb


             reply	other threads:[~2004-03-04 22:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04 22:02 Daniel Jacobowitz [this message]
2004-03-19  0:09 ` Daniel Jacobowitz

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=20040304220200.GA29799@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.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