Closed marghidanu closed 3 years ago
@marghidanu Please give a simple example (script and pp
command) so that I can reproduce your problem.
Sure thing, here's exactly what I use for my application:
pp ./scripts/app.pl
--output app
--compile
--lib lib
--module "Whatever::"
--module "MooseX::Log::Log4perl::"
--module "MooseX::Storage::"
--module "Mojo::"
--module "Mojolicious::Plugin::"
--addfile "/usr/local/share/perl5/site_perl/Mojo/resources/;lib/Mojo/resources/"
--addfile "/usr/local/share/perl5/site_perl/Mojo/IOLoop/resources/;lib/Mojo/IOLoop/resources/"
--addfile "/usr/local/share/perl5/site_perl/Mojolicious/resources/;lib/Mojolicious/resources/"
In this case, Mojolicious is the culprit.
It's a strange interaction between options "--compile" and "--module Foo::"
@marghidanu You could have saved me some time by posting your pp
recipe and the complete output of pp
in the initial issue (w/o me having to explicitly ask for it). Can you retry with PAR::Packer master?
If you need additional information for your bugfixes create an issue template explaining what you require or have a section in your readme.
The output is ok now.
Is there a way to suppress these types of messages?
Subroutine DESTROY redefined at /usr/local/share/perl5/site_perl/Mojo/IOLoop/Client.pm line 25
These are polluting the output of
pp