Windows 7

Could not find a suitable Class::Load implementation

I have a perl programs which works flawlessly on my computer, with Activestate perl 5.16.3 installed (32 bit, MS Windows 7, kernel 32 bit) and all the required modules.

I try to prepare a standalone executable with perlapp: the executable is created without any apparent issue. I run it in a separate console, and I get this error message.
Can't locate Path/Class/Entity.pm in @INC (@INC contains: ...
BEGIN failed--compilation aborted

That is easy: I explicitly include the module (in perlapp gui, menu Files, Added modules, ...)

PPM crashes after fresh install of Perl 5.16.3

On my Win 7/64-bit system, I did a clean uninstall of AS 5.16.1/64-bit, then a clean install of AS 5.16.3/64-bit.

When I then tried to run PPM, it immediately crashed.

I uninstalled, rebooted and reinstalled, same crash.

I uninstalled, deleted C:\Perl64 directory and then reinstalled, same crash.

I'm going to try 5.16.2 now. Any other suggestions?

Rick

Upgrading while keeping all your settings/modules intact

I discovered that my current AS perl, 5.12, is no longer ppm'able [without a business license] so I'm upgrading to 5.16. I'm worried about how that 'upgrade' should/will go. right now perl is installed in c:\perl64. Can I just install the new 5.16 in the same directory and will it basically leave my installed modules and other such along [perhaps needing a big update via ppm, but still there]? Or will I run into problems?

"Perl Command Line Interpreter has stopped working" when running PPM.

Can't get the PPM GUI to run. This is on Win 7 64-bit. Tried reinstalling 5.16.2 64-bit, with the same result. PPM command line seems to work. Just the GUI won't run. Tried 5.16.2 x86 and this launches the GUI fine.

The following is in the event log:
Faulting application name: perl.exe, version: 5.16.2.1602, time stamp: 0x50d17d90
Faulting module name: ole32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c92c
Exception code: 0xc0000005
Fault offset: 0x0000000000036b3b
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11

Can't create Executable for other Targets

I use ActivePerl 5.10.1007 for Win32 x86 and the PDK 9.0.1 to make executables from my perl scripts.

This works finde but now i need a linux script and tried to generate one. When i change the Target to Linux (x86) the message "PerlApp doesnt have a cached copy..." comes and PerlApp tries to download the ActivePerl 5.10.107 for Linux. This happens because i reinstalled my development pc with the new windows 7.

But now there comes the Message "Access to ActivePerl-5.10.1.1007-i686-linux-glibc-2.3.2-291969.tar.gz requires an ActivePerl Business Edition licence to be installed".

ActiveTcl Demos

Having just installed TCL 8.5.9, and using Teacup to install the Expect Pakage successfully, I can't find the Expect Demo. The documentatio indicates:

"Expect for Windows includes a number of demonstration applications to help you get started. These demos are installed in the demos\Expect directory beneath the Tcl installation directory (by default, C:\Tcl\demos\Expect)."

HOwever, the demos are not present here.

Cannot install Pycrypto on Python 2.7

I have installed both ActivePython-2.7.8.10-win64-x64.msi and ActivePython-2.7.8.10-win32-x86.msi and attempting to install Pycrypto I get the error "Python version 2.6 is required, which was not found in the registry."

Packaging Wx

Hello,

I'm using PDK 9.3 + ActivePerl 5.16 on both Windows (32-bit) and Linux (64-bit) and my question is what is the recommended way to package Wx applications using PerlApp?

Do we still need to do the Wx::Perl::Packager hackery to get the .dll/.so files included in the binary or does PerlApp have heuristics for that?

I am using Mark Dootson's Wx PPM repository and if I create a binary without Wx::Perl::Packager the Wx shared libraries are missing on runtime.

Thanks!

gmail api on windows pc

(I posted this question to the mailing-list and got the following response:

The reason it is being held:
Post by non-member to a members-only list

. So I'll try posting here.)

Outdated Node.js version in Stackato 3.4.1 - How to update?

I'm running a Nodejs application in Stackato 3.4.1 inside VirtualBox.
My app requires a pretty new node version >= 0.10.
However npm install reports that the node version is 0.8.26.

How can I upgrade to a newer nodejs version?

Even more confusing is, that when checking the node version in the admin console node -v returns v0.10.26.

Any ideas?

/klaus