On Tue, 28 Jun 2005, Marko Asplund wrote:
>  On 2005-06-28, at 10.00, Jan Dubois wrote:
>  >
>  > Please send complete output from running the command.
>  >
>  > Also, what does `perl -c foo` print?
>  
>  here's the output:
>  
>  [aspa@merlot fcgi]$ /opt/kronodoc/perl/kb3400ap2/bin/perl -c kronodoc
>  kronodoc syntax OK
>  
>  [aspa@merlot fcgi]$ /opt/kronodoc/perl/pdk601/bin/perlapp --depend --
>  exe kd.bin kronodoc
>  PerlApp 6.0.1 build 138984
>  Copyright (C) 1998-2005 ActiveState Corp.  All rights reserved.
>  ActiveState is a division of Sophos Plc.
>  Evaluation license for aspa <aspa@[...].com> (Expires: 2005-07-18)
>  
>  ************************************************************************
>  ****
>  * WARNING: Applications generated by this evaluation copy of PerlApp
>  will  *
>  *          stop working after the end of the evaluation period:
>  2005-07-18 *
>  ************************************************************************
>  ****
>  
>  'kronodoc' had compilation errors.

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`.

>  the script uses lots of other modules, do i need to specify these on
>  the perlapp command line?

No, that should normally not be necessary.  The error message above indicates
that PerlApp encountered syntax errors while checking your file.  It should have
printed thoses errors to STDERR before printing the '... had compilation errors.'
message, so maybe there is still some incompatibility between your Perl and
ActivePerl.

Cheers,
-Jan


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