Re: automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==)

On 2/1/25 16:23, Karl Berry wrote:
> I have to admit I don't much like any method Jacob mentioned, or
> anything else I can think of (sed ...) to munge core source files.
>
> I don't know about the past, but I've never knowingly ignored a Perl
> warning that's been reported or that I've seen. Going to these lengths
> to have fatal warnings in development seems like a cure worse than the
> disease to me. FWIW ... -k

I generally agree, especially since the Perl documentation explicitly 
discourages "use warnings FATAL => 'all';".

If the concern is making certain that new Perl warnings are noticed, 
simply putting PERL5OPT='-Mwarnings=FATAL,all' in the environment when 
running the testsuite should accomplish that. Run the testsuite once 
with that and once without and compare the results for each new Perl 
release.

Note that no special support in Automake should be needed for that, 
other than ensuring that the test driver honors an inherited PERL5OPT 
value instead of unsetting PERL5OPT.


-- Jacob