On 7 October 2014 16:07, Benjamin Fernandis <benjo11...@gmail.com> wrote:
> + Attaching log file. > Lacking Env.pm basically means your vendor's Perl is broken. Env.pm is shipped with Perl itself, and subsequently things may forget to depend on it ( at least, in a way that cpan tools recognise ) and be silently broken as a consequence. It *might* be worth filing a bug with the respective packages saying "hey, you need Env.pm, but dont depend on it" But the thing that will make life easiest for you is working out why you don't have things installed that are EXPECTED to be installed as part of a standard perl installation. But the general problem is, sometimes people in Perl have external dependencies and forget to declare them as such. When they do that, things break. When things break like that, if you're sure the problem is them failing to declare the dependency, then you file a bug requesting they declare the dependency. Once the dependency is declared, CPAN, CPANPLUS and cpanm will detect and respond to it. -- Kent *KENTNL* - https://metacpan.org/author/KENTNL
