X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=README.solaris;h=a2f189da9a9d378bf93b736cee28fe784d9a16cc;hb=8fa7688f7865696bdfa78bc12d4ffb78bd1d6103;hp=5231c0c39359a7fab6a1d7f62d41b84681280b1d;hpb=a83b6f466440987720492416f8091f2530a9ab41;p=p5sagit%2Fp5-mst-13.2.git diff --git a/README.solaris b/README.solaris index 5231c0c..a2f189d 100644 --- a/README.solaris +++ b/README.solaris @@ -42,12 +42,12 @@ number as reported by uname. Here's a partial translation table: SunOS 5.8 Solaris 8 solaris 2.8 The complete table can be found in the Sun Managers' FAQ -L under +L 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 +There are many, many sources for Solaris information. A few of the important ones for perl: =over 4 @@ -58,16 +58,16 @@ The Solaris FAQ is available at L. The Sun Managers' FAQ is available at -L +L =item Precompiled Binaries Precompiled binaries, links to many sites, and much, much more is -available at L. +available at L. =item Solaris Documentation -All Solaris documentation is available on-line at L. +All Solaris documentation is available on-line at L. =back @@ -81,7 +81,7 @@ for SunOS4 on Solaris. (GNU tar compiled for Solaris should be fine.) 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 found this advice it too late and used a SunOS4-compiled tar +If you found this advice too late and used a SunOS4-compiled tar anyway, you must find the incorrectly renamed file and move it back to lib/locale.pm. @@ -134,7 +134,7 @@ If you use Sun's C compiler, make sure the correct directory If you use gcc, make sure your installation is recent and complete. As a point of reference, perl-5.6.0 built fine with -gcc-2.8.1 on both Solaris 2.6 and Solaris 8. You'll be able to +gcc-2.8.1 on both Solaris 2.6 and Solaris 8. You should Configure perl with sh Configure -Dcc=gcc @@ -153,14 +153,31 @@ your Solaris release. =head3 GNU as and GNU ld +The following information applies to gcc version 2. Volunteers to +update it as appropropriate for gcc version 3 would be appreciated. + The versions of as and ld supplied with Solaris work fine for building -perl. There is normally no need to install the GNU versions. +perl. There is normally no need to install the GNU versions to +compile perl. If you decide to ignore this advice and use the GNU versions anyway, then be sure that they are relatively recent. Versions newer than 2.7 are apparently new enough. Older versions may have trouble with dynamic loading. +If you wish to use GNU ld, then you need to pass it the -Wl,-E flag. +The hints/solaris_2.sh file tries to do this automatically by executing +the following commands: + + ccdlflags="$ccdlflags -Wl,-E" + lddlflags="$lddlflags -Wl,-E -G" + +However, over the years, changes in gcc, GNU ld, and Solaris ld have made +it difficult to automatically detect which ld ultimately gets called. +You may have to manually edit config.sh and add the -Wl,-E flags +yourself, or else run Configure interactively and add the flags at the +appropriate prompts. + If your gcc is configured to use GNU as and ld but you want to use the Solaris ones instead to build perl, then you'll need to add -B/usr/ccs/bin/ to the gcc command line. One convenient way to do @@ -258,7 +275,7 @@ 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 -Developer's Guide at http://docs.sun.com:80/ab2/coll.45.13/SOL64TRANS/ +Developer's Guide at L You can detect the OS mode using "isainfo -v", e.g. @@ -270,7 +287,7 @@ 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 don't need Perl to be a 64-bit app. -=head3 Large File Suppprt +=head3 Large File Support For Solaris 2.6 and onwards, there are two different ways for 32-bit applications to manipulate large files (files whose size is > 2GByte). @@ -381,11 +398,11 @@ 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 +track down. Sun's compiler appears to be okay with or without perl's malloc. [XXX further investigation is needed here.] =head1 MAKE PROBLEMS. @@ -438,6 +455,10 @@ Building in /tmp sometimes shows this behavior. The test suite detects if you are building in /tmp, but it may not be able to catch all tmpfs situations. +=head2 nss_delete core dump from op/pwent or op/grent + +See L. + =head1 PREBUILT BINARIES OF PERL FOR SOLARIS. You can pick up prebuilt binaries for Solaris from @@ -483,13 +504,13 @@ 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. -=head2 BSD::Resource on Solairs +=head2 BSD::Resource on Solaris BSD::Resource versions earlier than 1.09 do not compile on Solaris 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 on Soalris +=head2 Net::SSLeay on Solaris 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