> > - shipping both a Makefile.PL and a Build.PL correctly is a tough > problem
Although I that I was using the deprecated "passthrough" style, using every combination listed in the docs <https://metacpan.org/pod/Module::Build::Compat#create_makefile_pl-style-build> a Makefile.PL was added to distribution tarball. I even tried omitting a line like "create_makefile_pl => 'traditional' . Although shipping both a Makefile.PL and a Build.PL may be a tough problem, having the program that invoke "make test" could set an environment variable such as PERL. And that would help the makefile and any scripts it runs to use the right perl. On Fri, Jul 1, 2016 at 10:29 PM, Andreas Koenig < andreas.koenig.7os6v...@franz.ak.mind.de> wrote: > >>>>> On Fri, 1 Jul 2016 22:15:43 -0400, Rocky Bernstein < > rocky.bernst...@gmail.com> said: > > > If it is the case that something in the smoker decided to invoke > > "/usr/bin/make test" as it appears above, then how is a makefile > > supposed to know which Perl is intended? > > - It depends on who wrote the makefile > - Makefiles written by ExtUtils::MakeMaker just know it. Typically they > set PERL correctly > - shipping both a Makefile.PL and a Build.PL correctly is a tough > problem > > -- > andreas >
