From: Jerome Guitton <guitton@adacore.com>
To: gdb-patches@sourceware.org, gcc-patches@gcc.gnu.org,
binutils@sourceware.org
Subject: [RFA] trailing backslash in top-level Makefile
Date: Tue, 02 Jun 2009 16:34:00 -0000 [thread overview]
Message-ID: <20090602163356.GB20678@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
The top-level Makefile.in may generate a trailing backslash at the end
of the target "all" (if gcc-bootstrap is false). Something like that:
[...]
all:
@: $(MAKE); $(unstage)
@r=`${PWD_COMMAND}`; export r; \
s=`cd $(srcdir); ${PWD_COMMAND}`; export s; \
$(MAKE) $(RECURSE_FLAGS_TO_PASS) all-host all-target \
.PHONY: all-build
[...]
On most system, that's fine. However, this is rejected by some shells.
For example, the system bash on some solaris systems:
ostende% bash --version
GNU bash, version 2.03.0(1)-release (sparc-sun-solaris)
Copyright 1998 Free Software Foundation, Inc.
> bash -c "ls \\"
bash: -c: line 2: syntax error: unexpected end of file
The patch in attachment would fix the problem. It's a little bit ugly
though. "echo" is used as a "nop". Would someone have a better idea to fix
the problem?
2009-06-02 Jerome Guitton <guitton@adacore.com>
* Makefile.tpl: Remove a trailing backslash.
* Makefile.in: Regenerate.
[-- Attachment #2: toplevel.diff --]
[-- Type: text/x-diff, Size: 1200 bytes --]
Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/Makefile.in,v
retrieving revision 1.302
diff -u -r1.302 Makefile.in
--- Makefile.in 2 Jun 2009 08:23:45 -0000 1.302
+++ Makefile.in 2 Jun 2009 15:18:31 -0000
@@ -859,11 +859,11 @@
$(MAKE) $(TARGET_FLAGS_TO_PASS) all-host all-target; \
else \
@endif gcc-bootstrap
- $(MAKE) $(RECURSE_FLAGS_TO_PASS) all-host all-target \
+ $(MAKE) $(RECURSE_FLAGS_TO_PASS) all-host all-target ; \
@if gcc-bootstrap
- ; \
fi
@endif gcc-bootstrap
+ echo
.PHONY: all-build
Index: Makefile.tpl
===================================================================
RCS file: /cvs/src/src/Makefile.tpl,v
retrieving revision 1.206
diff -u -r1.206 Makefile.tpl
--- Makefile.tpl 2 Jun 2009 08:23:45 -0000 1.206
+++ Makefile.tpl 2 Jun 2009 15:18:38 -0000
@@ -625,11 +625,11 @@
$(MAKE) $(TARGET_FLAGS_TO_PASS) all-host all-target; \
else \
@endif gcc-bootstrap
- $(MAKE) $(RECURSE_FLAGS_TO_PASS) all-host all-target \
+ $(MAKE) $(RECURSE_FLAGS_TO_PASS) all-host all-target ; \
@if gcc-bootstrap
- ; \
fi
@endif gcc-bootstrap
+ echo
.PHONY: all-build
[+ FOR build_modules +]
next reply other threads:[~2009-06-02 16:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 16:34 Jerome Guitton [this message]
2009-06-02 18:00 ` Ralf Wildenhues
2009-06-02 22:04 ` Ralf Wildenhues
2009-06-02 22:08 ` DJ Delorie
2009-06-03 6:16 ` Ralf Wildenhues
2009-06-02 23:16 ` Alexandre Oliva
2009-06-03 8:44 ` Jerome Guitton
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=20090602163356.GB20678@adacore.com \
--to=guitton@adacore.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--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