From: Paul Brook <paul@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: [patch] Missing $(EXEEXT)
Date: Wed, 27 Apr 2005 20:30:00 -0000 [thread overview]
Message-ID: <200504272130.02264.paul@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 228 bytes --]
The attached patch adds missing $(EXEEXT) to sim/common/Make-common.in
Tested by building i686-mingw32 hosted cross.
Ok?
Paul
2005-04-27 Paul Brook <paul@codesourcery.com>
* common/Make-common.in: Add $(EXEEXT) to "run".
[-- Attachment #2: patch.gdb_run_exe --]
[-- Type: text/x-diff, Size: 1112 bytes --]
Index: common/Make-common.in
===================================================================
RCS file: /var/cvsroot/src-cvs/src/sim/common/Make-common.in,v
retrieving revision 1.20
diff -u -p -r1.20 Make-common.in
--- common/Make-common.in 9 Feb 2005 22:04:04 -0000 1.20
+++ common/Make-common.in 27 Apr 2005 20:08:50 -0000
@@ -252,14 +252,14 @@ RUNTESTFLAGS =
callback_h = $(srcroot)/include/gdb/callback.h
remote_sim_h = $(srcroot)/include/gdb/remote-sim.h
-all: $(SIM_EXTRA_ALL) libsim.a run .gdbinit
+all: $(SIM_EXTRA_ALL) libsim.a run$(EXEEXT) .gdbinit
libsim.a: $(LIB_OBJS)
rm -f libsim.a
$(AR) $(AR_FLAGS) libsim.a $(LIB_OBJS)
$(RANLIB) libsim.a
-run: $(SIM_RUN_OBJS) libsim.a $(LIBDEPS)
+run$(EXEEXT): $(SIM_RUN_OBJS) libsim.a $(LIBDEPS)
$(CC) $(ALL_CFLAGS) -o run$(EXEEXT) \
$(SIM_RUN_OBJS) libsim.a $(EXTRA_LIBS)
@@ -646,7 +646,7 @@ TAGS: force
clean: $(SIM_EXTRA_CLEAN)
rm -f *.[oa] *~ core
- rm -f run libsim.a
+ rm -f run$(EXEEXT) libsim.a
rm -f gentmap targ-map.c targ-vals.h stamp-tvals
if [ ! -f Make-common.in ] ; then \
rm -f $(BUILT_SRC_FROM_COMMON) ; \
next reply other threads:[~2005-04-27 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 20:30 Paul Brook [this message]
2005-04-27 20:34 ` 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=200504272130.02264.paul@codesourcery.com \
--to=paul@codesourcery.com \
--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