ActiveState Community
Navigation
RSS Feeds
Solaris
DBD:ODBC + ActivePerl
Hi,
I have been looking at a problem one ouf our customers was having using ActivePerl to connect via DBD:ODBC to our SQL Server driver on Linux. After investigating, the problem seems to be that the version of iODBC you have built your distribution with expects the W (wide) functions (SQLDriverConnectW, SQLConnectW) to use four byte unicode. Unfortunatly that will fail with just about every ODBC driver out there that exports the W functions, as most of those will expect 2 byte wide characters, just the same as on Windows
Komodo on Solaris
Im evaluating the use of Komodo at my firm. We are in a mixed windows/solaris setting. However all of the coding occurs on the solaris side.
For Komodo to be usable in this setting I would need either:
1) A solaris version of Komodo. This seems to be gone.
2) A way to use the solaris interpreters within a win-Komodo debugger, shell etc... at a usable speed for a large codebase. The remote debugger binaries for Solaris seem to be gone as well.
Are either of these possible? Am I missing something?
Thanks!
Compiled Perlscript hangs on Solaris
Hi all
I have a strange problem with a compiled Perlscript on Solaris 9. After the script is finished it just hangs.
Script looks like this:
#!perl -w
use strict;
use Getopt::Std;
use Date::Manip;
use Mail::Sender;
use Config::General;
use Data::Dumper;
.... Does some stuff (and this behaves as expected)....
print "exiting...\n";
exit 0;
what happens is: It prints "exiting..." and then the prompt just hangs.
Here's the output of perlapp and perl -v:
------ Start Output ------
What's the difference between SunOS and Solaris?
What's the difference between SunOS and Solaris? What's a SPARC? Do SPARC packages run on Intel/x86?
The terms SunOS and Solaris both refer to the Solaris operating environment released by Sun Microsystems (http://www.sun.com/). Several years ago they were separate products, but now they are one and the same. SunOS was replaced in marketing material by Solaris, but there are still some places in a modern Solaris system where SunOS is made reference to (most notably in the output of "uname").
SunOS version numbers that might be seen today range from 4.x (pre-Solaris versions of SunOS) to 5.10 (which corresponds to Solaris 2.10 or Solaris 10).
Solaris version numbers that are common range from 2.5 (a.k.a. Solaris 5) to 2.10 (a.k.a. Solaris 10). The "2." prefix is not used in marketing material for Solaris -- it is only used internally.
Putting this all together, SunOS 5.10 is the same beast as Solaris 2.10 which is the same as Solaris 10.
As well as having multiple names and multiple version identifiers, Solaris runs primarily on two types of CPUs. One is the SPARC architecture, which is an advanced RISC architecture, and the other is the Intel/x86 architecture. Sun Microsystems is the primary source of SPARC-based systems, while the x86 version of Solaris runs on commodity IA32 (x86) and AMD x86_64 machines. The two machine types are not compatible; packages for SPARC will not run on x86, and vice versa.
A notable feature of Solaris is that modern versions of the operating system will often have no problems running programs built for earlier versions. For example, ActivePerl built on Solaris 6 will run without issue on Solaris 10. The converse is not true, however. Programs built on a given version of the system will usually not work on an earlier version.
Recently there has been an initiative called OpenSolaris (http://www.opensolaris.org/) that embodies the next version of Solaris. Currently code-named Nevada, it forms the basis for what will be Solaris 11 (a.k.a. Solaris 2.11, a.k.a. SunOS 5.11). Compatibility with software built for earlier versions of Solaris is expected to be mostly kept.
- Login to post comments
Unattended installation of ActivePerl in a custom directory on Solaris
I need to install ActivePerl in a custom directory on Solaris without any user interaction. How can I do that?
There are two ways to install ActivePerl in a custom directory on Solaris such that the installation can be run unattended.
The first is to use the "--license-accepted --prefix /path/to/install/to" arguments to the install.sh provided in the Tar/Gzip ActivePerl package:
gnutar zxf ActivePerl-solaris-package.tar.gz cd ActivePerl-directory sh install.sh --license-accepted --prefix /opt/ActiveState/ActivePerl
The above can be used in a shell script, for example.
Alternatively, you can make your own Solaris package. This has the benefit of registering ActivePerl with the Solaris packaging system, making upgrades easier in some cases. A good tutorial on making Solaris packages can be found here:
- Login to post comments
