Starting with Solaris 8, perl5.00503 (or higher) is supplied with the
operating system, so you might not even need to build a newer version
of perl at all. The Sun-supplied version is installed in /usr/perl5
-with a link to /usr/bin/perl. Do not disturb that installation unless
-you really know what you are doing. If you remove the perl supplied
-with the OS, there is a good chance you will render some bits of your
-system inoperable. If you wish to install a newer version of perl,
-install it under a different prefix from /usr/perl5. Common prefixes
-to use are /usr/local and /opt/perl.
+with /usr/bin/perl pointing to /usr/perl5/bin/perl. Do not disturb
+that installation unless you really know what you are doing. If you
+remove the perl supplied with the OS, there is a good chance you will
+render some bits of your system inoperable. If you wish to install a
+newer version of perl, install it under a different prefix from
+/usr/perl5. Common prefixes to use are /usr/local and /opt/perl.
+
+You may wish to put your version of perl in the PATH of all users by
+changing the symlink /usr/bin/perl. This is OK, as all Perl scripts
+shipped with Solaris use /usr/perl5/bin/perl.
=head2 Solaris Version Numbers.
Sun: perl's Configure:
uname uname -r Name osname osvers
- SunOS 4.1.3 SunOS 4.1.3 sunos 4.1.3
+ SunOS 4.1.3 Solaris 1.1 sunos 4.1.3
SunOS 5.6 Solaris 2.6 solaris 2.6
SunOS 5.8 Solaris 8 solaris 2.8
+The complete table can be found in the Sun Managers' FAQ
+L<ftp://ftp.cs.toronto.edu/pub/jdd/sun-managers/faq> under
+"9.1) Which Sun models run which versions of SunOS?".
+
=head1 RESOURCES
There are many, many source for Solaris information. A few of the
The Solaris FAQ is available at
L<http://www.science.uva.nl/pub/solaris/solaris2.html>.
+The Sun Managers' FAQ is available at
+L<ftp://ftp.cs.toronto.edu/pub/jdd/sun-managers/faq>
+
=item Precompiled Binaries
Precompiled binaries, links to many sites, and much, much more is
When you run SunOS4 binaries on Solaris, the run-time system magically
alters pathnames matching m#lib/locale# so that when tar tries to create
lib/locale.pm, a file named lib/oldlocale.pm gets created instead.
-If you ignore this advice and use a a SunOS4-compiled tar anyway, you
-must find the incorrectly renamed file and move it back to lib/locale.pm.
+If you found this advice it too late and used a SunOS4-compiled tar
+anyway, you must find the incorrectly renamed file and move it back
+to lib/locale.pm.
=head2 Compiler and Related Tools.
for 64 bit development: SUNWarcx, SUNWbtoox, SUNWdplx, SUNWscpux,
SUNWsprox, SUNWtoox, SUNWlmsx, SUNWlmx, SUNWlibCx
+If you are in doubt which package contains a file you are missing,
+try to find an installation that has that file. Then do a
+
+ grep /my/missing/file /var/sadm/install/contents
+
+This will display a line like this:
+
+/usr/include/sys/errno.h f none 0644 root bin 7471 37605 956241356 SUNWhea
+
+You need the package SUNWhea.
+
=head3 Avoid /usr/ucb/cc.
You don't need to have /usr/ucb/ in your PATH to build perl. If you
-want /usr/ucb/ in your PATH anyway, make sure that /usr/ucb/cc is NOT
-in your PATH before the real C compiler.
+want /usr/ucb/ in your PATH anyway, make sure that /usr/ucb/ is NOT
+in your PATH before the directory containing the right C compiler.
=head3 Sun's C Compiler
If you use Sun's C compiler, make sure the correct directory
-(usually /opt/SUNWspro/bin/) is in your PATH before /usr/ucb/.
+(usually /opt/SUNWspro/bin/) is in your PATH (before /usr/ucb/).
=head3 GCC
If you have updated your Solaris version, you may also have to update
your GCC. For example, if you are running Solaris 2.6 and your gcc is
installed under /usr/local, check in /usr/local/lib/gcc-lib and make
-sure you have the appropriate directory sparc-sun-solaris2.6/. If gcc's
-directory is for a different version of Solaris than you are running,
-then you will need to rebuild gcc for your new version of Solaris.
+sure you have the appropriate directory, sparc-sun-solaris2.6/ or
+i386-pc-solaris2.6/. If gcc's directory is for a different version of
+Solaris than you are running, then you will need to rebuild gcc for
+your new version of Solaris.
You can get a precompiled version of gcc from
-L<http://www.sunfreeware.com/>.
+L<http://www.sunfreeware.com/>. Make sure you pick up the package for
+your Solaris release.
=head3 GNU as and GNU ld
sh Configure -Dcc='gcc -B/usr/ccs/bin/'
Note that the trailing slash is required. This will result in some
-harmless error messages as Configure is run:
+harmless warnings as Configure is run:
gcc: file path prefix `/usr/ccs/bin/' never used
=head3 General 32-bit vs. 64-bit issues.
-Solaris 2.7 and above will run in either 32 bit or 64 bit mode, via a reboot.
-You can build 64 bit apps whilst running 32 bit mode and vice-versa.
-32 bit apps will run under Solaris running in either 32 or 64 bit mode.
-64 bit apps require Solaris to be running 64 bit mode
+Solaris 7 and above will run in either 32 bit or 64 bit mode on SPARC
+CPUs, via a reboot. You can build 64 bit apps whilst running 32 bit
+mode and vice-versa. 32 bit apps will run under Solaris running in
+either 32 or 64 bit mode. 64 bit apps require Solaris to be running
+64 bit mode
Existing 32 bit apps are properly known as LP32, i.e. Longs and
Pointers are 32 bit. 64-bit apps are more properly known as LP64.
The discriminating feature of a LP64 bit app is its ability to utilise a
64-bit address space. It is perfectly possible to have a LP32 bit app
-that supports both 64-bit integers (long long) and largefiles (> 2Gb),
+that supports both 64-bit integers (long long) and largefiles (> 2GB),
and this is the default for perl-5.6.0.
For a more complete explanation of 64-bit issues, see the Solaris 64-bit
32-bit sparc applications
By default, perl will be compiled as a 32-bit application. Unless you
-want to allocate more than ~ 4Gb of memory inside Perl, you probably
+want to allocate more than ~ 4GB of memory inside Perl, you probably
don't need Perl to be a 64-bit app.
=head3 Large File Suppprt
For Solaris 2.6 and onwards, there are two different ways for 32-bit
-applications to manipulate large files (files whose size is > 2Gbyte).
+applications to manipulate large files (files whose size is > 2GByte).
(A 64-bit application automatically has largefile support built in
by default.)
_XBS5_LPBIG_OFFBIG_LINTFLAGS: -xarch=v9
This flag is supported in Sun WorkShop Compilers 5.0 and onwards when
-used on Solaris 2.7 onwards.
+used on Solaris 7 onwards.
+
+If you are using gcc, you would need to use -mcpu=v9 -m64 instead. This
+option is not yet supported as of gcc 2.95.2; from install/SPECIFIC
+in that release:
-If you are using gcc, you need to use -mcpu=v9 -m64 instead. This
-option is not supported in the installation of gcc-2.8.1 that I have
-at hand, but is supported in more recent versions. [XXX -- any
-precise citations?]
+GCC version 2.95 is not able to compile code correctly for sparc64
+targets. Users of the Linux kernel, at least, can use the sparc32
+program to start up a new shell invocation with an environment that
+causes configure to recognize (via uname -a) the system as sparc-*-*
+instead.
All this should be handled automatically by the hints file, if
requested.
-If you do want to be able to allocate more than 4Gb memory inside
+If you do want to be able to allocate more than 4GB memory inside
perl, then you should use the Solaris malloc, since the perl
-malloc breaks when dealing with more than 2Gb of memory. You can do
+malloc breaks when dealing with more than 2GB of memory. You can do
this with
sh Configure -Uusemymalloc
You should also not use perl's malloc if you are building perl as
an LP64 application, since perl's malloc has trouble allocating more
-than 2Gb of memory.
+than 2GB of memory.
You can avoid perl's malloc by Configuring with
sh Configure -Uusemymalloc
+[XXX Update hints file.]
+
=head1 MAKE PROBLEMS.
=over 4
=head1 PREBUILT BINARIES.
You can pick up prebuilt binaries for Solaris from
-L<http://www.sunfreeware.com>, ActiveState L<http://www.activestate.com>,
-and L<http://www.perl.com> under the Binaries list at the top of the page.
+L<http://www.sunfreeware.com/>, ActiveState L<http://www.activestate.com/>,
+and L<http://www.perl.com/> under the Binaries list at the top of the page.
There are probably other sources as well. Please note that these sites
are under the control of their respective owners, not the perl developers.
A fix for Proc::ProcessTable is to edit Makefile to
explicitly remove the largefile flags from the ones MakeMaker picks up
from Config.pm. This will result in Proc::ProcessTable being built
-under the correct environment. Everyting should then be OK as long as
+under the correct environment. Everything should then be OK as long as
Proc::ProcessTable doesn't try to share off_t's with the rest of perl,
or if it does they should be explicitly specified as off64_t.
with perl 5.6.0 and higher, for the same reasons as Proc::ProcessTable.
BSD::Resource versions starting from 1.09 have a workaround for the problem.
+=head2 Net::SSLeay
+
+Net::SSLeay requires a /dev/urandom to be present. This device is not
+part of Solaris. You can either get the package SUNWski (packaged with
+several Sun software products, for example the Sun WebServer, which is
+part of the Solaris Server Intranet Extension, or the Sun Directory
+Services, part of Solaris for ISPs) or download the ANDIrand package
+from L<http://www.cosy.sbg.ac.at/~andi/>. If you use SUNWski, make a
+symbolic link /dev/urandom pointing to /dev/random.
+
+It may be possible to use the Entropy Gathering Daemon (written in
+Perl!), available from L<http://www.lothar.com/tech/crypto/>.
+
=head1 AUTHOR
The original was written by Andy Dougherty F<doughera@lafayette.edu>
projects / p5sagit/p5-mst-13.2.git / commitdiff