From ae452a4116476cf9ed17b73c8df51492ce7624da Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Mon, 18 Sep 2023 10:15:13 +0000 Subject: makefile: avoid needless use of double-colon rules This non-portable construct isn't needed for our own rules. I'm understanding them correctly, they have different semantics between *BSDs and GNU make. --- Makefile.PL | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'Makefile.PL') diff --git a/Makefile.PL b/Makefile.PL index 9dc18b5c..81992e46 100644 --- a/Makefile.PL +++ b/Makefile.PL @@ -213,7 +213,7 @@ $VARS -include Documentation/include.mk $TGTS -check-man :: $check_lexgrog$warn_no_pod +check-man : $check_lexgrog$warn_no_pod # syntax checks are currently GNU make only: %.syntax :: % @@ -231,24 +231,24 @@ check-manifest : MANIFEST \$(check_manifest) # the traditional way running per-*.t processes: -check-each :: pure_all +check-each : pure_all \$(EATMYDATA) \$(PROVE) --state=save -bvw -j\$(N) -@\$(check_manifest) # check-run relies "--state=save" in check-each for best performance -check-run :: check-man +check-run : check-man # n.b. while `-' isn't specified as an allowed make(1posix) macro name, # GNU and *BSD both allow it. check-run_T_ARGS = -j\$(N) -check-debris check-run :: pure_all +check-debris check-run : pure_all \$(EATMYDATA) \$(PROVE) -bvw xt/\$@.t :: \$(\$\@_T_ARGS) -@\$(check_manifest) -check :: check-each +check : check-each -lib/PublicInbox/UserContent.pm :: contrib/css/216dark.css +lib/PublicInbox/UserContent.pm : contrib/css/216dark.css \$(PERL) -I lib \$@ \$? # Ensure new .pm files will always be installed by updating @@ -269,7 +269,7 @@ symlink-install : lib/PublicInbox.pm ln -sf "\$\$lei" \$\$(basename "\$\$x"); \\ done -pure_all :: lib/PublicInbox.pm +pm_to_blib : lib/PublicInbox.pm lib/PublicInbox.pm : FORCE VERSION=\$(VERSION) \$(PERL) -w ./version-gen.perl -- cgit v1.2.3-24-ge0c7