The probe was checking the severity bits of the compiler exit
status and requiring the value to be 1, which is what they are
for SS$_NORMAL. But actually any true (odd) value is considered
successful. So, for example, if the compile succeeds but emits
"informational messages" that do not rise to the level of warnings
or errors, the severity bits have a value of 3, not 1. The probe
should not fail (and end up halting the build) in this case, so
allow any successful value.
'Time::HiRes' => {
'DISTRIBUTION' => 'ATOOMIC/Time-HiRes-1.9764.tar.gz',
'FILES' => q[dist/Time-HiRes],
+ 'CUSTOMIZED' => [
+ qw( Makefile.PL ),
+ ],
},
'Time::Local' => {
open( CMDFILE, '>', "$tmp.com" );
print CMDFILE "\$ SET MESSAGE/NOFACILITY/NOSEVERITY/NOIDENT/NOTEXT\n";
print CMDFILE "\$ $cccmd\n";
- print CMDFILE "\$ IF \$SEVERITY .NE. 1 THEN EXIT 44\n"; # escalate
+ print CMDFILE "\$ IF .NOT. \$SEVERITY THEN EXIT 44\n"; # escalate
close CMDFILE;
system("\@ $tmp.com");
$ok = $?==0;
Net::Ping dist/Net-Ping/t/501_ping_icmpv6.t 54373de5858f8fb7e078e4998a4b3b8dbca91783
Pod::Perldoc cpan/Pod-Perldoc/lib/Pod/Perldoc.pm 582be34c077c9ff44d99914724a0cc2140bcd48c
Test::Harness cpan/Test-Harness/t/source.t aaa3939591114c0c52ecd44159218336d1f762b9
+Time::HiRes dist/Time-HiRes/Makefile.PL a8c1da5ec1672780e453304925ee0615b422c61f
Win32API::File cpan/Win32API-File/File.pm 8fd212857f821cb26648878b96e57f13bf21b99e
Win32API::File cpan/Win32API-File/File.xs beb870fed4490d2faa547b4a8576b8d64d1d27c5
experimental cpan/experimental/t/basic.t cb9da8dd05b854375809872a05dd32637508d5da