ActiveState Community Site - Solaris - Comments

lanch installation

webkamelo_yahoo — Tue, 04 Nov 2008 03:24:53 -0800

file installer do not lanching automaticly
msi do not start

ODBC Connection works on Command line, but not in Web Browser

andrew2404 — Wed, 17 Sep 2008 07:57:46 -0700

I have a perl app that happily retrieves from a MS-SQL database when run on the command line. However, when I run it from a web browser nothing is displayed. It fails to connect to the database

It must be due to the browser not running as "my user" and running as the "web user", which does not have permission to connect. Where can I check this?

I feel that I'm really close. HELP:>

Many thanks in advance.

--use option

grahams — Thu, 06 Mar 2008 14:57:30 -0800

I think you get the hangs because the PDK is compiling with a different version of libperl.so than your executable uses at runtime.

Here is the telltale:

libperl.so at '/opt/ActivePerl-5.8/lib/5.8.7/sun4-solaris-thread-multi/CORE/libperl.so' is not compatible with the PDK.
Using '/opt/pdk/lib/libperl.so' instead.

The explanation for what is going on comes out of the Release Notes:
The PDK now uses a dynamically linked libperl.so on Unix instead of including statically linked libperl.a in each generated executable. This allowed implementation of the --xclude option for Unix, and --dependent and --xclude applications are much smaller now.
Only libperl.so from ActivePerl 819 and later is fully compatible with the new mechanism. PerlApp will use its own bundled libperl.so for older versions of ActivePerl. It also bundles a special libperl.so to use with Perl 5.6.

Updating to a newer version of ActivePerl would fix the issue. Or you could set PerlApp's --use option to force the executable to use the same libperl.so that it was compiled with, and the odd behavior will probably go away.

Should you consider copying the PDK libperl.so elsewhere, be careful to place it where it won't interfere with the 815 version of libperl.so, or the compatibility problems could go the other way.

Re: Komodo on Solaris

ToddW — Thu, 21 Feb 2008 16:44:30 -0800

Sorry for the lat reply, but here are the answers to your questions:

1) Is there a solaris version of Komodo?
No, since Komodo 4, ActiveState has dropped support for Komodo on Solaris. From what I understand, there was not enough demand to match the resources cost.

2) Remote debugger binaries for Solaris?
Most (if not all, I'm not quite sure for tcl) of the debugger downloads are not actually binaries, but operate in pure source form, so taking any of the linux download packages can be used for remote debugging purposes on a solaris machine, connecting to the Komodo application running on the Win/Mac/Linux host.

Cheers,
Todd

Possibilities

troyt — Thu, 21 Feb 2008 16:41:52 -0800

Solaris support, including updated remote debugging libraries, was discontinued as of Komodo 4.0. That said, there are some things you can try:

The Solaris 10 documentation seems to suggest that most Linux binaries should be able to run on x86 systems:

http://www.sun.com/software/solaris/ds/linux_interop.jsp

If you're on x86, it's definitely worth a try.

If that doesn't work for you, you may still be able to get remote debugging libraries to work:

The Perl libraries are pure-perl, so they should run fine on Solaris

http://aspn.activestate.com/ASPN/Downloads/Komodo/RemoteDebugging

The PHP debugger is xdebug, which can be compiled from source:

http://xdebug.org/

Likewise, the ruby-debug can be compiled from source:

https://rubyforge.org/projects/ruby-debug/

If none of that works, you could try the Komodo 3.5 Remote Debugging Packages for Solaris:

http://aspn.activestate.com/ASPN/Downloads/Komodo/RemoteDebugging

(under "Komodo 3.5 Remote Debugging Packages")

Komodo 4 should be mostly backwards compatible with these libraries, but this has not been tested.

Hope this helps.