openssl/util/echo.pl

#! /usr/bin/env perl

use strict;
use warnings;
use Getopt::Std;

our $opt_n = 0;

getopts('n') or die "Invalid option: $!\n";

print join(' ', @ARGV);
print "\n" unless $opt_n;
always use the same perl in $PATH Different tests may use unexpectedly different versions of perl, depending on whether they hardcode the path to the perl executable or if they resolve the path from the environment. This fixes it so that the same perl is always used. Fix some trailing whitespace and spelling mistakes as well. CLA: trivial Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Paul Dale <pauli@openssl.org> (Merged from https://github.com/openssl/openssl/pull/16362) 2021-08-19 19:05:15 +08:00			`#! /usr/bin/env perl`
Windows: fix echo for nmake It seems that nmake first tries to run executables on its own, and only pass commands to cmd if that fails. That means it's possible to have nmake run something like 'echo.exe' when the builtin 'echo' command was expected, which might give us unexpected results. To get around this, we create our own echoing script and call it explicitly from the nmake makefile. Fixes #6670 Reviewed-by: Andy Polyakov <appro@openssl.org> Reviewed-by: Bernd Edlinger <bernd.edlinger@hotmail.de> (Merged from https://github.com/openssl/openssl/pull/6686) 2018-07-10 20:12:33 +08:00
			`use strict;`
			`use warnings;`
			`use Getopt::Std;`

			`our $opt_n = 0;`

			`getopts('n') or die "Invalid option: $!\n";`

			`print join(' ', @ARGV);`
			`print "\n" unless $opt_n;`