(Sending to the PAR list, as I neglected to include it in my initial response).
If you can work out which packages the function calls come from then you can check the packed executable to see if it contains them. If they are not included then they have been missed in the module scan process. They can be added using the -M argument to pp. Are you able to provide some cut-down example code to test on other machines? Roderich is far more qualified than me to comment on the code signing fix and your other related points. Regards, Shawn. On Sat, 15 Jun 2019 at 18:15, welle ozean <welleoz...@googlemail.com> wrote: > Hi Shawn, > > module version is 1.048. Note that I also use pp_osx_codesign_fix > <https://github.com/rschupp/PAR-Packer/tree/master/contrib/pp_osx_codesign_fix> > (in contributions on GitHub) before release because of macOS codesigning. > Please, also note that the call to a different Perl is to load PAR.pm > which, as far I can tell, is a prerequisite for my executable to run (my > executable runs, i.e. GUI is initialized, but fails on some function > calls). Note that the very same application (executable) works fine on most > machines with the same OS. I am tempted to think - but it is just > speculation for the moment - that something may be wrong with Archive::Zip > and the pre-release fix. Even if this does not explain why the problem > occurs only on some machines. I am a bit in the blue right now, as you can > see. > > I am indagating the cause of the problem also with the Tcl::pTk module > maintainer as the error comes from that module. > > > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > Virenfrei. > www.avg.com > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > <#m_-2807865423814341314_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > Am Sa., 15. Juni 2019 um 03:11 Uhr schrieb Shawn Laffan < > shawnlaf...@gmail.com>: > >> A couple of points. >> >> Which version of PAR are you using? >> >> The call to a different perl is sometimes due to missing dependencies or >> other files at the packing stage. Have you checked the set that has been >> packed? >> >> Also, the code you gave does not look correct. It is using the numeric >> not-equals operator to compare $retVal against a string. >> Is this from your code or within Tk? >> >> Shawn. >> >> >> >> On Sat, 15 Jun 2019 at 04:40, welle ozean via par <par@perl.org> wrote: >> >>> Hello, >>> >>> I have a GUI application (written in Tcl::pTk) compiled as an executable >>> for macOS (Mojave). On some machines I get the following error (I can not >>> replicate it on mine) which I think may be related to pp/PAR and not with >>> the rest of the software (but I may be wrong). Could somebody point me to >>> the right direction? >>> >>> Tcl::pTk::Error: Illegal division by zero at (eval 183) line 37. >>> >>> while executing >>> "if {$catchVal != 0} { >>> if { $retVal != "_TK_BREAK_\n" } { # BREAK >>> returns are not errors >>> return..." >>> (command bound to event) >>> >>> Error Started at script/MYPROGRAM.pl line 206. >>> >>> Stack Trace: >>> at Tcl/pTk.pm line 923. >>> eval {...} called at Tcl/pTk.pm line 923 >>> Tcl::pTk::DoOneEvent(Tcl::pTk=SCALAR(0x7fcff0f88698), 0) called at >>> Tcl/pTk.pm line 906 >>> Tcl::pTk::MainLoop() called at script/MYPROGRAM.pl line 206 >>> require main called at >>> /Users/we/perl5/perlbrew/perls/perl-5.26.1/lib/site_perl/5.26.1/PAR.pm line >>> 645 >>> PAR::_run_member(Archive::Zip::ZipFileMember=HASH(0x7fcfec6621f0), 1) >>> called at script/main.pl line 26 >>> require main called at >>> /Users/we/perl5/perlbrew/perls/perl-5.26.1/lib/site_perl/5.26.1/PAR.pm line >>> 645 >>> PAR::_run_member(Archive::Zip::ZipFileMember=HASH(0x7fcfec6624d8)) >>> called at >>> /Users/we/perl5/perlbrew/perls/perl-5.26.1/lib/site_perl/5.26.1/PAR.pm line >>> 432 >>> PAR::import("PAR") called at -e line 585 >>> eval {...} called at -e line 41 >>> __par_pl::BEGIN() called at script/MYPROGRAM.pl line 0 >>> eval {...} called at script/MYPROGRAM.pl line 0 >>> >>> By the way, why is the application trying to call something in >>> "Users/we/perl5/perlbrew" which is a path in the machine where I compiled >>> the application? >>> >>> Thank you for any suggestion >>> Claudio >>> >>
