X-Git-Url: https://perl5.git.perl.org/perl5.git/blobdiff_plain/f858446f8d2c74c0a4665f0be04b65fe90e1b08c..9d9b1dc8244316e9c017c8694e94d467e7d41c21:/README.solaris diff --git a/README.solaris b/README.solaris index cc5fbbf..b3003c1 100644 --- a/README.solaris +++ b/README.solaris @@ -4,7 +4,7 @@ specifically designed to be readable as is. =head1 NAME -README.solaris - Perl version 5 on Solaris systems +perlsolaris - Perl version 5 on Solaris systems =head1 DESCRIPTION @@ -18,7 +18,7 @@ For the most part, everything should just work. 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 /usr/bin/perl pointing to /usr/perl5/bin/perl. Do not disturb +with F pointing to F. Do not disturb that installation unless you really know what you are doing. If you remove the perl supplied with the OS, you will render some bits of your system inoperable. If you wish to install a newer version of perl, @@ -26,9 +26,9 @@ 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 link /usr/bin/perl. This is probably OK, as most perl +changing the link F. This is probably OK, as most perl scripts shipped with Solaris use an explicit path. (There are a few -exceptions, such as /usr/bin/rpm2cpio and /etc/rcm/scripts/README, but +exceptions, such as F and F, but these are also sufficiently generic that the actual version of perl probably doesn't matter too much.) @@ -143,18 +143,25 @@ shipped with SunOS4 will not do. Several tools needed to build perl are located in /usr/ccs/bin/: ar, as, ld, and make. Make sure that /usr/ccs/bin/ is in your PATH. -You need to make sure the following packages are installed -(this info is extracted from the Solaris FAQ): + +On all the released versions of Solaris (8, 9 and 10) you need to make sure the following packages are installed (this info is extracted from the Solaris FAQ): for tools (sccs, lex, yacc, make, nm, truss, ld, as): SUNWbtool, SUNWsprot, SUNWtoo for libraries & headers: SUNWhea, SUNWarc, SUNWlibm, SUNWlibms, SUNWdfbh, -SUNWcg6h, SUNWxwinc, SUNWolinc +SUNWcg6h, SUNWxwinc + +Additionally, on Solaris 8 and 9 you also need: for 64 bit development: SUNWarcx, SUNWbtoox, SUNWdplx, SUNWscpux, SUNWsprox, SUNWtoox, SUNWlmsx, SUNWlmx, SUNWlibCx +And only on Solaris 8 you also need: + +for libraries & headers: SUNWolinc + + 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 @@ -477,20 +484,20 @@ malloc. [XXX further investigation is needed here.] If you have problems with dynamic loading using gcc on SunOS or Solaris, and you are using GNU as and GNU ld, see the section -L<"GNU as and GNU ld"> above. +L above. =item ld.so.1: ./perl: fatal: relocation error: If you get this message on SunOS or Solaris, and you're using gcc, it's probably the GNU as or GNU ld problem in the previous item -L<"GNU as and GNU ld">. +L. =item dlopen: stub interception failed The primary cause of the 'dlopen: stub interception failed' message is that the LD_LIBRARY_PATH environment variable includes a directory which is a symlink to /usr/lib (such as /lib). See -L<"LD_LIBRARY_PATH"> above. +L above. =item #error "No DATAMODEL_NATIVE specified" @@ -514,7 +521,7 @@ directory. =head2 op/stat.t test 4 in Solaris -op/stat.t test 4 may fail if you are on a tmpfs of some sort. +F test 4 may fail if you are on a tmpfs of some sort. 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. @@ -523,6 +530,20 @@ to catch all tmpfs situations. See L. +=head1 CROSS-COMPILATION + +Nothing too unusual here. You can easily do this if you have a +cross-compiler available; A usual Configure invocation when targetting a +Solaris x86 looks something like this: + + sh ./Configure -des -Dusecrosscompile \ + -Dcc=i386-pc-solaris2.11-gcc \ + -Dsysroot=$SYSROOT \ + -Alddlflags=" -Wl,-z,notext" \ + -Dtargethost=... # The usual cross-compilation options + +The lddlflags addition is the only abnormal bit. + =head1 PREBUILT BINARIES OF PERL FOR SOLARIS. You can pick up prebuilt binaries for Solaris from @@ -543,7 +564,7 @@ through 255 can be used in a stream. Since perl calls open() and then fdopen(3C) with the resulting file descriptor, perl is limited to 255 simultaneous open files, even if sysopen() is used. If this proves to be an insurmountable problem, you can compile perl as a -LP64 application, see L for details. Note +LP64 application, see L for details. Note also that the default resource limit for open file descriptors on Solaris is 255, so you will have to modify your ulimit or rctl (Solaris 9 onwards) appropriately. @@ -594,7 +615,7 @@ L. If you use SUNWski, make a symbolic link /dev/urandom pointing to /dev/random. For more details, see Document ID27606 entitled "Differing /dev/random support requirements within Solaris[TM] Operating Environments", available at -http://sunsolve.sun.com . +L . It may be possible to use the Entropy Gathering Daemon (written in Perl!), available from L. @@ -609,14 +630,14 @@ GNU ld gets very unhappy and spews a lot of errors like this ... relocation truncated to fit: BASE13 ... and dies. Therefore the SunOS 4.1 hints file explicitly sets the -ld to be /usr/bin/ld. +ld to be F. As of Perl 5.8.1 the dynamic loading of libraries (DynaLoader, XSLoader) also seems to have become broken in in SunOS 4.x. Therefore the default is to build Perl statically. Running the test suite in SunOS 4.1 is a bit tricky since the -F test hangs (subtest #51, FWIW) for some +F test hangs (subtest #51, FWIW) for some unknown reason. Just stop the test and kill that particular Perl process. @@ -673,7 +694,8 @@ but if one patiently waits, one gets these results: uni/tr_eucjp.t 29 7424 6 12 200.00% 1-6 uni/tr_sjis.t 29 7424 6 12 200.00% 1-6 56 tests and 467 subtests skipped. - Failed 27/811 test scripts, 96.67% okay. 1383/75399 subtests failed, 98.17% okay. + Failed 27/811 test scripts, 96.67% okay. 1383/75399 subtests failed, + 98.17% okay. The alarm() test failure is caused by system() apparently blocking alarm(). That is probably a libc bug, and given that SunOS 4.x