aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlejandro Colomar <alx@kernel.org>2023-03-10 13:21:12 +0100
committerAlejandro Colomar <alx@kernel.org>2023-03-10 13:21:14 +0100
commit0440d04f831796e92d968422b8c49941e046cb8a (patch)
tree43759d7634f5a179eca2b7e9690a19f0f8e36116
parente728d5d1e639e5c803a84480ad727e7b02bac222 (diff)
downloadman-pages-0440d04f831796e92d968422b8c49941e046cb8a.tar.gz
lint-man.mk: lint-man-groff-eqn: Fix error detection
eqn(1) could theoretically write _only_ newlines to standard error. That's unlikely, but I'm still worried that someone (even me) might copy this trick around, and use it in situations where that might actually happen. Let's be more precise, and fail when there's literally anything on standard error. Reported-by: Ralph Corderoy <ralph@inputplus.co.uk> Signed-off-by: Alejandro Colomar <alx@kernel.org>
-rw-r--r--lib/lint-man.mk2
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/lint-man.mk b/lib/lint-man.mk
index 0583964b4c..d47aadc718 100644
--- a/lib/lint-man.mk
+++ b/lib/lint-man.mk
@@ -96,7 +96,7 @@ $(_LINT_man_groff_eqn): %.eqn: %.tbl | $$(@D)/.
$(_LINT_man_groff_troff): %.troff: %.eqn | $$(@D)/.
$(info LINT (eqn) $@)
$(EQN) $(EQNFLAGS) <$< 2>&1 >$@ \
- | ( ! $(GREP) . )
+ | ( ! $(GREP) ^ )
$(_LINT_man_groff_grotty): %.grotty: %.troff | $$(@D)/.
$(info LINT (troff) $@)