tests fail when cc is not in the path

[shawnlaffan]

(Edit) This is on Windows but seems to affect other systems. The matrix in cpan testers gives an overview.

http://matrix.cpantesters.org/?dist=ExtUtils-CppGuess+0.27

Commit 5e47504 added some mocked results and an override for ExtUtils::CppGuess::_capture but it seems not to trap all the variations.

The final test config at

extutils-cppguess/t/002_icpp.t

Lines 135 to 144 in bfbed58

	[
	{ cc => "cc", config => { ccflags => '' } },
	{
	is_sunstudio => 0,
	is_msvc => undef, is_gcc => 1, is_clang => 0,
	compiler_command => 'g++ -xc++',
	linker_flags => '-lstdc++',
	},
	{ "cc --version" => "cc (Debian 12.2.0-14) 12.2.0" },
	],

is causing an untrapped error at

extutils-cppguess/t/002_icpp.t

Line 158 in bfbed58

my %got = map {$_ => $guess->$_} @METHODS;

I've not been able to track down the root cause but it seems related to the checks at

extutils-cppguess/lib/ExtUtils/CppGuess.pm

Lines 288 to 300 in bfbed58

	if (!%guess) {
	my $v1 = `$c_compiler -v`;
	my $v2 = `$c_compiler -V`;
	my $v3 = `$c_compiler --version`;
	my $os = $self->_os;
	die <<EOF;
	Unable to determine a C++ compiler for '$c_compiler' on $os
	Version attempts:
	-v: '$v1'
	-V: '$v2'
	--version: '$v3'
	EOF
	}

[mohawk2]

As noted on shawnlaffan/perl-alien-proj#9 - what do you think this module should do when it can't find a C++ compiler?

Separately, are you saying this non-finding is wrong? Where is the C++ compiler installed that this module should have looked?

[shawnlaffan]

These are tested using Strawberry Perl, which has g++ in its path.

The issue here is that the tests are mocking c++ compiler output but not mocking the search for the cc compiler when the is_gcc flag is true. There is no cc compiler on the system and so the test fails.

[shawnlaffan]

Looping back to this.

The issue here is that the mocking used in the test is incomplete. The test failure is a false negative wrt the module working or not, i.e. it correctly detects the g++ that comes with Strawberry Perl.

The simplest thing to do is to skip this test case when run under Strawberry Perl. This can be detected using $Config{myuname} =~ /strawberry/.