From: Jason R Thorpe <thorpej@wasabisystems.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH/RFA] Fix NATDEPFILES sed expression to comment out cont's
Date: Fri, 10 May 2002 14:58:00 -0000 [thread overview]
Message-ID: <20020510145819.K3435@dr-evil.shagadelic.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
The following was submitted as a bug report to NetBSD. The sed
expression that comments out NATDEPFILES does not comment out
continuation lines. BSD's make(1) doesn't like this (the \ at
the end of the line is ignored, just as the rest of the line following
the comment character is, as it should be).
The following tweak to the sed expression fixes the problem by also
commenting out continuation lines.
Before:
# NATDEPFILES=infptrace.o inftarg.o fork-child.o \
corelow.o \
alphabsd-nat.o alphanbsd-nat.o
After:
# NATDEPFILES= infptrace.o inftarg.o fork-child.o \
# corelow.o \
# alphabsd-nat.o alphanbsd-nat.o
OK to commit?
2002-05-10 Christian Limpach <chris@Pin.LU>
* configure.in: Change sed expression which comments out
NATDEPFILES to also comment out continuation lines.
* configure: Regenerate.
--
-- Jason R. Thorpe <thorpej@wasabisystems.com>
[-- Attachment #2: configure-patch --]
[-- Type: text/plain, Size: 660 bytes --]
Index: configure.in
===================================================================
RCS file: /cvs/src/src/gdb/configure.in,v
retrieving revision 1.86
diff -u -r1.86 configure.in
--- configure.in 11 Apr 2002 18:32:50 -0000 1.86
+++ configure.in 10 May 2002 21:51:29 -0000
@@ -1366,7 +1366,8 @@
dnl
if test "${nativefile}" = ""; then
< Makefile \
- sed -e '/^NATDEPFILES[[ ]]*=[[ ]]*/s//# NATDEPFILES=/' \
+ sed -e '/^NATDEPFILES[[ ]]*=.*\\$/,/[[^\\]]$/s/^/# /' \
+ -e '/^NATDEPFILES[[ ]]*=/s/^/# /' \
| sed -e '/^\(NATDEPFILES[[ ]]*[[+]]=[[ ]]*\)/s//# \1/' \
> Makefile.tem
mv -f Makefile.tem Makefile
next reply other threads:[~2002-05-10 21:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 14:58 Jason R Thorpe [this message]
2002-05-10 16:50 ` Andrew Cagney
2002-05-10 17:40 ` Jason R Thorpe
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=20020510145819.K3435@dr-evil.shagadelic.org \
--to=thorpej@wasabisystems.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