On Tue, 28 Jun 2005, Marko Asplund wrote:
>  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?

You can use --lib to add those additional @INC directories to the PerlApp
search path.
 
>  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.

With PDK 6 you can also use the --perl option to tell PerlApp which perl
version to use.
 
>  I've attached a typescript of the compilation and the test run with
>  full error messages.

It seems like you need to specify additional options to Configure to build
an ActivePerl compatible perl:

You'll need to add at least "-Accflags=-DNO_HASH_SEED", but I found 2 others
you should probably add:

-Dusethreads -Duseithreads -Ud_sigsetjmp -Duselargefiles -Accflags=-DNO_HASH_SEED

This should even fix your syntax checking issue, I would hope.

Cheers,
-Jan


_______________________________________________
PDK mailing list
PDK@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs