I've been unsuccessful in getting my Perl Dev Kit 9.3 build 297998 running properly. Initially upon installation it would not run because the version of Perl I had installed earlier was version 5.10 (incompatible).
I uninstalled Perl 5.10 and installed 5.18.2 build 1802. I repaired the installation of the Perl Dev Kit and again attempted to run PerlApp. Now it reported that "C:\Program Files (x86)\ActiveState Perl Dev Kit 9.3\bin\perlapp.exe is not recognized as a PDK tool."
PerlApp 9.3.0 build 298063
libperl.dylib at '/System/Library/Perl/5.18/darwin-thread-multi-2level/CORE/libperl.dylib' is not compatible with the PDK.
OS X 10.10 Yosemite
I purchased pdk version 9 a couple years ago and it ran OK with perl 5.12. Recently I installed perl 5.16 and I'm getting "The program can't start because perl512.dll is missing..." Will it work if I put perl512.dll in my Windows 7 path?
Attempting to Launch latest 9.3 version of PerlApp...it crashes and leaves this in the console log:
9/15/14 8:02:45.803 AM PerlApp: An uncaught exception was raised
9/15/14 8:02:45.803 AM PerlApp: Error (1000) creating window shape
9/15/14 8:02:45.804 AM PerlApp: (
0 CoreFoundation 0x00007fff8639025c __exceptionPreprocess + 172
1 libobjc.A.dylib 0x00007fff88c08e75 objc_exception_throw + 43
2 CoreFoundation 0x00007fff8639010c +[NSException raise:format:] + 204
3 AppKit 0x00007fff8ce8c9b9 _NSCreateWindowWithOpaqueShape2 + 159
I purchased PDK 18.104.22.1685 many, many years ago (~2000) and running on a Windows 98 machine that died.
Tried to install on a Windows 7 machine. While everything seemed to install properly, it didn't add Perl to PATH and said I have to do so manually.
As a result, I can't invoke Perl to run programs off of the MS DOS window, and can't compile using Perlapp
Any suggestions on how to manually add Perl to PATH?
Pdk 9.2.1 Build 296433
I had a working version of active perl but the windows 7 system I am using has been patched recently after that I am getting the below incompatability error.
C:\WORK\PERL-SCRIPTS\STORAGE\STORAGE1>perlapp --tmpdir /usr/ecc
/smbc/tmp --norunlib --target linux-x86-64 --exe vplexrestapi.exe vplexrestapi.p
'C:\Program Files (x86)\ActiveState\ActivePerl\Perl32\bin\perl.exe' (MSWin32-x86
-multi-thread-64int) is not binary compatible with ActivePerl (MSWin32-x86-multi
Any help is much appreciated.
I'm getting a perl debugger warning pop up (see attachment) when installing our licensed version of your Perl Dev Kit 6.0. Its an old (possibly 32bit) installer that we have used over the years.
The warming pop up is an empty warning message. Normally I wouldnt worry about this too much, but the debugger wont start. When trying to start the debugger the error message is "Failed to start the ActiveState Perl Debugger. Please ensure that the activestate perl debuger is properly installed and try again".
Just purchased the license for $300 and reinstall the PDK. But the the license is still the eval version. There is no where to prompt me install the license.
I just uninstalled Perl 5.16 and installed 5.18. Also, I uninstalled PDK 9.2.1 and installed PDK 9.3.
After upgrading Perl and PDK, when I open the Mail::Sender (sender.pm) module I get this errors:
Can't load 'C:/Perl/site/lib/auto/Encode/Encode.dll' for module Encode: load_file:The specified module could not be found at C:/Perl/lib/XSLoader.pm line 68.
at C:/Perl/site/lib/Encode.pm line 10.
Compilation failed in require at C:/Perl/site/lib/Mail/Sender.pm line 27.
BEGIN failed--compilation aborted at C:/Perl/site/lib/Mail/Sender.pm line 27.
The PDK delivers different results when __FILE__ is used in a file vs when used in an external package. This is PDK 3.0 with Perl 5.16 on Windows 7 - this has been replicated on Mac and Windows 8.
The .PL and .PM and the associated Makefile are provided in the attached zip