diff options
| author | Craig A. Berry <craigberry@mac.com> | 2020-12-24 08:48:47 -0600 |
|---|---|---|
| committer | Craig A. Berry <craigberry@mac.com> | 2020-12-24 12:01:59 -0600 |
| commit | 9eebd4ca7bb8610f51a27d96c12e9b1676958d55 (patch) | |
| tree | 0da70498a3e7b14850296d82524a4302d88f9a39 /Porting | |
| parent | 387608880ebf5408efb63a7fbd36309dd17758d8 (diff) | |
| download | perl-9eebd4ca7bb8610f51a27d96c12e9b1676958d55.tar.gz | |
Fix Time::HiRes compile probe on VMS
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.
Diffstat (limited to 'Porting')
| -rwxr-xr-x | Porting/Maintainers.pl | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/Porting/Maintainers.pl b/Porting/Maintainers.pl index 66330fe4f4..ed248761c7 100755 --- a/Porting/Maintainers.pl +++ b/Porting/Maintainers.pl @@ -1206,6 +1206,9 @@ use File::Glob qw(:case); 'Time::HiRes' => { 'DISTRIBUTION' => 'ATOOMIC/Time-HiRes-1.9764.tar.gz', 'FILES' => q[dist/Time-HiRes], + 'CUSTOMIZED' => [ + qw( Makefile.PL ), + ], }, 'Time::Local' => { |