From: Guy Harris <guy@alum.mit.edu>
Date: Wed, 5 Feb 2020 09:07:52 +0000 (-0800)
Subject: Don't assume a Perl script can be run directly as a command.
X-Git-Tag: tcpdump-4.99-bp~547
X-Git-Url: https://git.tcpdump.org/tcpdump/commitdiff_plain/74224d189c21428c84747a4cfd7c13621f30f95c?ds=sidebyside

Don't assume a Perl script can be run directly as a command.

That's not the case on Windows - it doesn't support #!.  Look for the
perl interpreter and, if we find it, add a rule that runs tests/TESTrun
with the interpreter.
---

diff --git a/CMakeLists.txt b/CMakeLists.txt
index b946c17d..626f090a 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -1200,6 +1200,15 @@ add_custom_target(uninstall
 
 #
 # Tcpdump tests
-#
-add_custom_target(check
-    COMMAND ${CMAKE_SOURCE_DIR}/tests/TESTrun)
+# We try to find the Perl interpreter and, if we do, we have the check
+# rule run tests/TESTrun with it, because just trying to run the TESTrun
+# script as a command won't work on Windows.
+#
+find_program(PERL perl)
+if(PERL)
+    message(STATUS "Found perl at ${PERL}")
+    add_custom_target(check
+        COMMAND ${PERL} ${CMAKE_SOURCE_DIR}/tests/TESTrun)
+else()
+    message(STATUS "Didn't find perl")
+endif()