On 2005-06-29, at 02.50, Jan Dubois wrote:
>  Weird.  You could try using the --nocheck option to see if PerlApp  
>  will create
>  a working executable, even if the syntax checking seems to be failing.
> 
>  Could you try building your executable with ActivePerl to see if it  
>  generates
>  the same error?  If it does, please also send the output of  
>  `perlapp --version
>  --verbose`.

I tried it with the --nocheck option and now PerlApp is able to  
produce an executable with some warnings about not being able to  
locate certain modules. Some of the modules which can't be located  
are there but apparantly PerlApp can't find them. The application  
sets up @INC paths in the BEGIN block to find these modules but  
PerlApp seems to have problems with this method. Some modules are  
referenced but not actually used by the application (e.g. APR/ 
Pool.pm). How should i handle these issues with PerlApp?

I also tried running the resulting executable but that fails with an  
error message about an undefined symbol. I had to add the ActivePerl  
perl as first component in my path in order for the executable to  
pick up the correct perl binary.

I've attached a typescript of the compilation and the test run with  
full error messages.

I'm not sure if i understand what you mean with trying to build my  
application with ActivePerl. Are you referring to using perlcc?


br. aspa