From: Sergei Trofimovich <slyich@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, Sergei Trofimovich <slyich@gmail.com>
Subject: [PATCH] mk: don't escape '#' for `grep`
Date: Thu, 27 Feb 2025 09:21:42 +0000 [thread overview]
Message-ID: <20250227092142.1822609-1-slyich@gmail.com> (raw)
Without the change build process complains
$ LANG=C make -R help
grep: warning: stray \ before #
grep: warning: stray \ before #
Signed-off-by: Sergei Trofimovich <slyich@gmail.com>
---
share/mk/configure/build-depends/cpp/cpp.mk | 2 +-
share/mk/src/sh.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/share/mk/configure/build-depends/cpp/cpp.mk b/share/mk/configure/build-depends/cpp/cpp.mk
index ef12a848a..8a4ccc442 100644
--- a/share/mk/configure/build-depends/cpp/cpp.mk
+++ b/share/mk/configure/build-depends/cpp/cpp.mk
@@ -21,7 +21,7 @@ endif
CPP_HAS_ALREADY_D_FORTIFY_SOURCE := \
$(shell \
$(CPP) -dM - -Wno-error </dev/null \
- | $(GREP) '\#define _FORTIFY_SOURCE ' >/dev/null \
+ | $(GREP) '#define _FORTIFY_SOURCE ' >/dev/null \
&& $(ECHO) yes \
|| $(ECHO) no; \
)
diff --git a/share/mk/src/sh.mk b/share/mk/src/sh.mk
index 05c9e0449..487eaf14d 100644
--- a/share/mk/src/sh.mk
+++ b/share/mk/src/sh.mk
@@ -14,7 +14,7 @@ include $(MAKEFILEDIR)/configure/directory_variables/src.mk
BIN_sh := $(shell $(FIND) $(SRCBINDIR) -type f \
- | $(XARGS) $(GREP) -l '^\#!/bin/\(sh\|bash\)\>' \
+ | $(XARGS) $(GREP) -l '^#!/bin/\(sh\|bash\)\>' \
| $(SORT))
--
2.48.1
next reply other threads:[~2025-02-27 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 9:21 Sergei Trofimovich [this message]
2025-02-27 10:23 ` [PATCH] mk: don't escape '#' for `grep` Alejandro Colomar
2025-02-27 11:23 ` Sergei Trofimovich
2025-02-27 12:28 ` Alejandro Colomar
2025-02-27 14:43 ` Florian Weimer
2025-02-27 15:20 ` Alejandro Colomar
2025-02-27 16:28 ` Jakub Wilk
2025-02-27 19:00 ` Alejandro Colomar
2025-02-27 19:30 ` Alejandro Colomar
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=20250227092142.1822609-1-slyich@gmail.com \
--to=slyich@gmail.com \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.