/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
+changing the link /usr/bin/perl. This is OK, as all Perl scripts
shipped with Solaris use /usr/perl5/bin/perl.
=head2 Solaris Version Numbers.
/usr/include/sys/errno.h f none 0644 root bin 7471 37605 956241356 SUNWhea
-You need the package SUNWhea.
+The last item listed (SUNWhea in this example) is the package you need.
=head3 Avoid /usr/ucb/cc.
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
+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.
=head3 Building an LP64 Perl
-To compile a 64-bit application with a recent Sun Compiler, you need to
-use the flag "-xarch=v9". getconf(1) will tell you this, e.g.
+To compile a 64-bit application on an UltraSparc with a recent Sun Compiler,
+you need to use the flag "-xarch=v9". getconf(1) will tell you this, e.g.
fubar$ getconf -a | grep v9
XBS5_LP64_OFF64_CFLAGS: -xarch=v9
_XBS5_LPBIG_OFFBIG_LDFLAGS: -xarch=v9
_XBS5_LPBIG_OFFBIG_LINTFLAGS: -xarch=v9
-This flag is supported in Sun WorkShop Compilers 5.0 and onwards when
-used on Solaris 7 onwards.
+This flag is supported in Sun WorkShop Compilers 5.0 and onwards
+(now marketed under the name Forte) when used on Solaris 7 or later on
+UltraSparc systems.
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
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
-perl, then you should use the Solaris malloc, since the perl
-malloc breaks when dealing with more than 2GB of memory. You can do
-this with
-
- sh Configure -Uusemymalloc
-
=head3 Long Doubles.
As of 5.6.0, long doubles are not working.
=head2 Malloc Issues.
+Starting from Perl 5.7.1 Perl uses the Solaris malloc, since the perl
+malloc breaks when dealing with more than 2GB of memory, and the Solaris
+malloc also seems to be faster.
+
+If you for some reason (such as binary backward compatibility) really
+need to use perl's malloc, you can rebuild Perl from the sources
+and Configure the build with
+
+ sh Configure -Dusemymalloc
+
You should not use perl's malloc if you are building with gcc. There
are reports of core dumps, especially in the PDL module. The problem
appears to go away under -DDEBUGGING, so it has been difficult to
track down. Sun's compiler appears to be ok with or without perl's
malloc. [XXX further investigation is needed here.]
-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.
-
-You can avoid perl's malloc by Configuring with
-
- sh Configure -Uusemymalloc
-
-[XXX Update hints file.]
-
=head1 MAKE PROBLEMS.
=over 4
=head1 LAST MODIFIED
-$Id: README.solaris,v 1.3 2000/11/09 19:11:27 doughera Exp $
+$Id: README.solaris,v 1.4 2000/11/11 20:29:58 doughera Exp $