in reply to Warnings when trying to install Pod::Coverage::Moose

This error is created by Build.PL when any prerequisite raised an error. Ideally, there would be a list of additional error messages at the bottom of the output:

my %errors = map { eval "require $_; $_->VERSION($configure_requires{$_}); 1"; $_ => $@, } keys %configure_requires; if (!grep $_, values %errors) { # This section for Pod-Coverage-Moose was generated by Dist::Zilla +::Plugin::ModuleBuildTiny 0.017. use strict; use warnings; use 5.006; # use Module::Build::Tiny 0.034; Module::Build::Tiny::Build_PL(); } else { if (not $ENV{PERL_MB_FALLBACK_SILENCE_WARNING}) { warn <<'EOW' *** WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING ** +* ... You can also silence this warning for future installations by setting +the PERL_MB_FALLBACK_SILENCE_WARNING environment variable, but please don' +t do that until you fix your toolchain as described above. Errors from configure prereqs: EOW . do { require Data::Dumper; Data::Dumper->new([ \%errors ])->Ind +ent(2)->Terse(1)->Sortkeys(1)->Dump; }; sleep 10 if -t STDIN && (-t STDOUT || !(-f STDOUT || -c STDOUT +)); }

The weird thing is that the section starting with

Errors from configure prereqs:

... is missing, as are the actual error messages. So I guess that what we are seeing is not the whole truth or that Data::Dumper output went to STDOUT and that is not shown.

Replies are listed 'Best First'.
Re^2: Warnings when trying to install Pod::Coverage::Moose
by choroba (Cardinal) on Nov 26, 2024 at 17:23 UTC
    > This error is created by Build.PL when any prerequisite raised an error.

    And the relevant part of Build.PL seems to be generated by Dist::Zilla::Plugin::ModuleBuildTiny::Fallback, if I'm not mistaken.

    map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]
Re^2: Warnings when trying to install Pod::Coverage::Moose
by Haarg (Priest) on Nov 27, 2024 at 06:26 UTC
    The warning is actually from the Makefile.PL file. It exists as a fallback, but a properly behaving CPAN client (or other tool that installs modules) should always prefer a Build.PL if it exists.
      but a properly behaving CPAN client (or other tool that installs modules) should always prefer a Build.PL if it exists

      May I ask where that is documented? I explicitly prefer the Makefile.PL way of doing things.

        I explicitly prefer the Makefile.PL way of doing things.

        Yes, me too.
        And the suggestion that some ad-hoc method of installing modules from CPAN should take precedence over a procedure that's already in the perl CORE is (at best) counter-intuitive.

        Cheers,
        Rob