Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro_alves@portugalmail.pt>
To: gdb-patches@sourceware.org
Subject: [gdbserver] Add EXEEXT; fix make clean.
Date: Sun, 25 Feb 2007 18:23:00 -0000	[thread overview]
Message-ID: <45E1D410.8060903@portugalmail.pt> (raw)

[-- Attachment #1: Type: text/plain, Size: 253 bytes --]

Hi all,

Another small patch;  This one fixes the clean rule for win32 hosts.

Ok?

Cheers,
Pedro Alves

---
gdb/gdbserver/ChangeLog:

2007-02-25  Pedro Alves  <pedro_alves@portugalmail.pt>

    * Makefile.in (EXEEXT): New.
    (clean): Use $(EXEEXT).


[-- Attachment #2: gdbserver_clean.diff --]
[-- Type: text/plain, Size: 774 bytes --]

Index: src/gdb/gdbserver/Makefile.in
===================================================================
--- src.orig/gdb/gdbserver/Makefile.in	2007-02-25 12:46:40.000000000 +0000
+++ src/gdb/gdbserver/Makefile.in	2007-02-25 18:09:54.000000000 +0000
@@ -44,6 +44,7 @@
 includedir = @includedir@
 
 SHELL = /bin/sh
+EXEEXT = @EXEEXT@
 
 INSTALL = @INSTALL@
 INSTALL_PROGRAM = @INSTALL_PROGRAM@
@@ -210,7 +211,7 @@
 clean:
 	rm -f *.o ${ADD_FILES} *~
 	rm -f version.c
-	rm -f gdbserver gdbreplay core make.log
+	rm -f gdbserver$(EXEEXT) gdbreplay$(EXEEXT) core make.log
 	rm -f reg-arm.c reg-i386.c reg-ia64.c reg-m32r.c reg-m68k.c reg-mips.c
 	rm -f reg-ppc.c reg-sh.c reg-spu.c reg-x86-64.c reg-i386-linux.c
 	rm -f reg-cris.c reg-crisv32.c reg-x86-64-linux.c reg-mips64.c

             reply	other threads:[~2007-02-25 18:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-25 18:23 Pedro Alves [this message]
2007-02-25 19:35 ` 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=45E1D410.8060903@portugalmail.pt \
    --to=pedro_alves@portugalmail.pt \
    --cc=gdb-patches@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