Re^3: Very Odd Issue When Using pp to Create an .exe File Including Date::Calc


Think about Loose Coupling
	PerlMonks

Re^3: Very Odd Issue When Using pp to Create an .exe File Including Date::Calc

by marto (Cardinal)

on Jun 27, 2017 at 19:57 UTC ( [id://1193720]=note: print w/replies, xml )

Need Help??

in reply to Re^2: Very Odd Issue When Using pp to Create an .exe File Including Date::Calc
in thread Very Odd Issue When Using pp to Create an .exe File Including Date::Calc

I'm mobile at the moment, so can't test further right now. However, a few things. Calling pp with -vvv this enables the highest level of verbose output. With the -L flag, provided with a file name this becomes the log for output, rather that stdout. See the documentation for various options. You could enable logging to discover the packaging process, compare the process for the different options and track down the reason from there. Similarly, extracting each exe into a directory will allow you to explore and compare the output. Comparing logs is probably easier :)

Comment on Re^3: Very Odd Issue When Using pp to Create an .exe File Including Date::Calc Select or Download Code

Replies are listed 'Best First'.

Re^4: Very Odd Issue When Using pp to Create an .exe File Including Date::Calc
by perldigious (Priest) on Jun 27, 2017 at 21:28 UTC

Cool, and no worries, mobile or not it's nice of you to take a look at it at all. I always just use "> some_log_name.txt" at the end of any Windows command line input when I want to shunt to some log file instead of STDOUT, but of course if the script expects inputs you have to know them and the order they are expected since the prompts are shunted there as well. :-)

Just another Perl hooker - But the purist monks keep telling me I should do it for love, not money.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom