| 1 |
.\" -*- mode: troff; coding: utf-8 -*- |
| 2 |
.\" Automatically generated by Pod::Man 5.0102 (Pod::Simple 3.45) |
| 3 |
.\" |
| 4 |
.\" Standard preamble: |
| 5 |
.\" ======================================================================== |
| 6 |
.de Sp \" Vertical space (when we can't use .PP) |
| 7 |
.if t .sp .5v |
| 8 |
.if n .sp |
| 9 |
.. |
| 10 |
.de Vb \" Begin verbatim text |
| 11 |
.ft CW |
| 12 |
.nf |
| 13 |
.ne \\$1 |
| 14 |
.. |
| 15 |
.de Ve \" End verbatim text |
| 16 |
.ft R |
| 17 |
.fi |
| 18 |
.. |
| 19 |
.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>. |
| 20 |
.ie n \{\ |
| 21 |
. ds C` "" |
| 22 |
. ds C' "" |
| 23 |
'br\} |
| 24 |
.el\{\ |
| 25 |
. ds C` |
| 26 |
. ds C' |
| 27 |
'br\} |
| 28 |
.\" |
| 29 |
.\" Escape single quotes in literal strings from groff's Unicode transform. |
| 30 |
.ie \n(.g .ds Aq \(aq |
| 31 |
.el .ds Aq ' |
| 32 |
.\" |
| 33 |
.\" If the F register is >0, we'll generate index entries on stderr for |
| 34 |
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index |
| 35 |
.\" entries marked with X<> in POD. Of course, you'll have to process the |
| 36 |
.\" output yourself in some meaningful fashion. |
| 37 |
.\" |
| 38 |
.\" Avoid warning from groff about undefined register 'F'. |
| 39 |
.de IX |
| 40 |
.. |
| 41 |
.nr rF 0 |
| 42 |
.if \n(.g .if rF .nr rF 1 |
| 43 |
.if (\n(rF:(\n(.g==0)) \{\ |
| 44 |
. if \nF \{\ |
| 45 |
. de IX |
| 46 |
. tm Index:\\$1\t\\n%\t"\\$2" |
| 47 |
.. |
| 48 |
. if !\nF==2 \{\ |
| 49 |
. nr % 0 |
| 50 |
. nr F 2 |
| 51 |
. \} |
| 52 |
. \} |
| 53 |
.\} |
| 54 |
.rr rF |
| 55 |
.\" ======================================================================== |
| 56 |
.\" |
| 57 |
.IX Title "PERLTRU64 1" |
| 58 |
.TH PERLTRU64 1 2025-11-16 "perl v5.40.1" "Perl Programmers Reference Guide" |
| 59 |
.\" For nroff, turn off justification. Always turn off hyphenation; it makes |
| 60 |
.\" way too many mistakes in technical documents. |
| 61 |
.if n .ad l |
| 62 |
.nh |
| 63 |
.SH NAME |
| 64 |
perltru64 \- Perl version 5 on Tru64 (formerly known as Digital UNIX formerly known as DEC OSF/1) systems |
| 65 |
.SH DESCRIPTION |
| 66 |
.IX Header "DESCRIPTION" |
| 67 |
This document describes various features of HP's (formerly Compaq's, |
| 68 |
formerly Digital's) Unix operating system (Tru64) that will affect |
| 69 |
how Perl version 5 (hereafter just Perl) is configured, compiled |
| 70 |
and/or runs. |
| 71 |
.SS "Compiling Perl 5 on Tru64" |
| 72 |
.IX Subsection "Compiling Perl 5 on Tru64" |
| 73 |
The recommended compiler to use in Tru64 is the native C compiler. |
| 74 |
The native compiler produces much faster code (the speed difference is |
| 75 |
noticeable: several dozen percentages) and also more correct code: if |
| 76 |
you are considering using the GNU C compiler you should use at the |
| 77 |
very least the release of 2.95.3 since all older gcc releases are |
| 78 |
known to produce broken code when compiling Perl. One manifestation |
| 79 |
of this brokenness is the lib/sdbm test dumping core; another is many |
| 80 |
of the op/regexp and op/pat, or ext/Storable tests dumping core |
| 81 |
(the exact pattern of failures depending on the GCC release and |
| 82 |
optimization flags). |
| 83 |
.PP |
| 84 |
Both the native cc and gcc seem to consume lots of memory when |
| 85 |
building Perl. toke.c is a known trouble spot when optimizing: |
| 86 |
256 megabytes of data section seems to be enough. Another known |
| 87 |
trouble spot is the mktables script which builds the Unicode support |
| 88 |
tables. The default setting of the process data section in Tru64 |
| 89 |
should be one gigabyte, but some sites/setups might have lowered that. |
| 90 |
The configuration process of Perl checks for too low process limits, |
| 91 |
and lowers the optimization for the toke.c if necessary, and also |
| 92 |
gives advice on how to raise the process limits |
| 93 |
(for example: \f(CW\*(C`ulimit \-d 262144\*(C'\fR) |
| 94 |
.PP |
| 95 |
Also, Configure might abort with |
| 96 |
.PP |
| 97 |
.Vb 2 |
| 98 |
\& Build a threading Perl? [n] |
| 99 |
\& Configure[2437]: Syntax error at line 1 : \*(Aqconfig.sh\*(Aq is not expected. |
| 100 |
.Ve |
| 101 |
.PP |
| 102 |
This indicates that Configure is being run with a broken Korn shell |
| 103 |
(even though you think you are using a Bourne shell by using |
| 104 |
"sh Configure" or "./Configure"). The Korn shell bug has been reported |
| 105 |
to Compaq as of February 1999 but in the meanwhile, the reason ksh is |
| 106 |
being used is that you have the environment variable BIN_SH set to |
| 107 |
\&'xpg4'. This causes /bin/sh to delegate its duties to /bin/posix/sh |
| 108 |
(a ksh). Unset the environment variable and rerun Configure. |
| 109 |
.SS "Using Large Files with Perl on Tru64" |
| 110 |
.IX Subsection "Using Large Files with Perl on Tru64" |
| 111 |
In Tru64 Perl is automatically able to use large files, that is, |
| 112 |
files larger than 2 gigabytes, there is no need to use the Configure |
| 113 |
\&\-Duselargefiles option as described in INSTALL (though using the option |
| 114 |
is harmless). |
| 115 |
.SS "Threaded Perl on Tru64" |
| 116 |
.IX Subsection "Threaded Perl on Tru64" |
| 117 |
If you want to use threads, you should primarily use the Perl |
| 118 |
5.8.0 threads model by running Configure with \-Duseithreads. |
| 119 |
.PP |
| 120 |
Perl threading is going to work only in Tru64 4.0 and newer releases, |
| 121 |
older operating releases like 3.2 aren't probably going to work |
| 122 |
properly with threads. |
| 123 |
.PP |
| 124 |
In Tru64 V5 (at least V5.1A, V5.1B) you cannot build threaded Perl with gcc |
| 125 |
because the system header <pthread.h> explicitly checks for supported |
| 126 |
C compilers, gcc (at least 3.2.2) not being one of them. But the |
| 127 |
system C compiler should work just fine. |
| 128 |
.SS "Long Doubles on Tru64" |
| 129 |
.IX Subsection "Long Doubles on Tru64" |
| 130 |
You cannot Configure Perl to use long doubles unless you have at least |
| 131 |
Tru64 V5.0, the long double support simply wasn't functional enough |
| 132 |
before that. Perl's Configure will override attempts to use the long |
| 133 |
doubles (you can notice this by Configure finding out that the \fBmodfl()\fR |
| 134 |
function does not work as it should). |
| 135 |
.PP |
| 136 |
At the time of this writing (June 2002), there is a known bug in the |
| 137 |
Tru64 libc printing of long doubles when not using "e" notation. |
| 138 |
The values are correct and usable, but you only get a limited number |
| 139 |
of digits displayed unless you force the issue by using \f(CW\*(C`printf |
| 140 |
"%.33e",$num\*(C'\fR or the like. For Tru64 versions V5.0A through V5.1A, a |
| 141 |
patch is expected sometime after perl 5.8.0 is released. If your libc |
| 142 |
has not yet been patched, you'll get a warning from Configure when |
| 143 |
selecting long doubles. |
| 144 |
.SS "DB_File tests failing on Tru64" |
| 145 |
.IX Subsection "DB_File tests failing on Tru64" |
| 146 |
The DB_File tests (db\-btree.t, db\-hash.t, db\-recno.t) may fail you |
| 147 |
have installed a newer version of Berkeley DB into the system and the |
| 148 |
\&\-I and \-L compiler and linker flags introduce version conflicts with |
| 149 |
the DB 1.85 headers and libraries that came with the Tru64. For example, |
| 150 |
mixing a DB v2 library with the DB v1 headers is a bad idea. Watch |
| 151 |
out for Configure options \-Dlocincpth and \-Dloclibpth, and check your |
| 152 |
/usr/local/include and /usr/local/lib since they are included by default. |
| 153 |
.PP |
| 154 |
The second option is to explicitly instruct Configure to detect the |
| 155 |
newer Berkeley DB installation, by supplying the right directories with |
| 156 |
\&\f(CW\*(C`\-Dlocincpth=/some/include\*(C'\fR and \f(CW\*(C`\-Dloclibpth=/some/lib\*(C'\fR \fBand\fR before |
| 157 |
running "make test" setting your LD_LIBRARY_PATH to \fI/some/lib\fR. |
| 158 |
.PP |
| 159 |
The third option is to work around the problem by disabling the |
| 160 |
DB_File completely when build Perl by specifying \-Ui_db to Configure, |
| 161 |
and then using the BerkeleyDB module from CPAN instead of DB_File. |
| 162 |
The BerkeleyDB works with Berkeley DB versions 2.* or greater. |
| 163 |
.PP |
| 164 |
The Berkeley DB 4.1.25 has been tested with Tru64 V5.1A and found |
| 165 |
to work. The latest Berkeley DB can be found from <http://www.sleepycat.com>. |
| 166 |
.SS "64\-bit Perl on Tru64" |
| 167 |
.IX Subsection "64-bit Perl on Tru64" |
| 168 |
In Tru64 Perl's integers are automatically 64\-bit wide, there is |
| 169 |
no need to use the Configure \-Duse64bitint option as described |
| 170 |
in INSTALL. Similarly, there is no need for \-Duse64bitall |
| 171 |
since pointers are automatically 64\-bit wide. |
| 172 |
.SS "Warnings about floating-point overflow when compiling Perl on Tru64" |
| 173 |
.IX Subsection "Warnings about floating-point overflow when compiling Perl on Tru64" |
| 174 |
When compiling Perl in Tru64 you may (depending on the compiler |
| 175 |
release) see two warnings like this |
| 176 |
.PP |
| 177 |
.Vb 4 |
| 178 |
\& cc: Warning: numeric.c, line 104: In this statement, floating\-point |
| 179 |
\& overflow occurs in evaluating the expression "1.8e308". (floatoverfl) |
| 180 |
\& return HUGE_VAL; |
| 181 |
\& \-\-\-\-\-\-\-\-\-\-\-^ |
| 182 |
.Ve |
| 183 |
.PP |
| 184 |
and when compiling the POSIX extension |
| 185 |
.PP |
| 186 |
.Vb 4 |
| 187 |
\& cc: Warning: const\-c.inc, line 2007: In this statement, floating\-point |
| 188 |
\& overflow occurs in evaluating the expression "1.8e308". (floatoverfl) |
| 189 |
\& return HUGE_VAL; |
| 190 |
\& \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-^ |
| 191 |
.Ve |
| 192 |
.PP |
| 193 |
The exact line numbers may vary between Perl releases. The warnings |
| 194 |
are benign and can be ignored: in later C compiler releases the warnings |
| 195 |
should be gone. |
| 196 |
.PP |
| 197 |
When the file \fIpp_sys.c\fR is being compiled you may (depending on the |
| 198 |
operating system release) see an additional compiler flag being used: |
| 199 |
\&\f(CW\*(C`\-DNO_EFF_ONLY_OK\*(C'\fR. This is normal and refers to a feature that is |
| 200 |
relevant only if you use the \f(CW\*(C`filetest\*(C'\fR pragma. In older releases of |
| 201 |
the operating system the feature was broken and the NO_EFF_ONLY_OK |
| 202 |
instructs Perl not to use the feature. |
| 203 |
.SH "Testing Perl on Tru64" |
| 204 |
.IX Header "Testing Perl on Tru64" |
| 205 |
During "make test" the \f(CW\*(C`comp\*(C'\fR/\f(CW\*(C`cpp\*(C'\fR will be skipped because on Tru64 it |
| 206 |
cannot be tested before Perl has been installed. The test refers to |
| 207 |
the use of the \f(CW\*(C`\-P\*(C'\fR option of Perl. |
| 208 |
.SH "ext/ODBM_File/odbm Test Failing With Static Builds" |
| 209 |
.IX Header "ext/ODBM_File/odbm Test Failing With Static Builds" |
| 210 |
The ext/ODBM_File/odbm is known to fail with static builds |
| 211 |
(Configure \-Uusedl) due to a known bug in Tru64's static libdbm |
| 212 |
library. The good news is that you very probably don't need to ever |
| 213 |
use the ODBM_File extension since more advanced NDBM_File works fine, |
| 214 |
not to mention the even more advanced DB_File. |
| 215 |
.SH "Perl Fails Because Of Unresolved Symbol sockatmark" |
| 216 |
.IX Header "Perl Fails Because Of Unresolved Symbol sockatmark" |
| 217 |
If you get an error like |
| 218 |
.PP |
| 219 |
.Vb 1 |
| 220 |
\& Can\*(Aqt load \*(Aq.../OSF1/lib/perl5/5.8.0/alpha\-dec_osf/auto/IO/IO.so\*(Aq for module IO: Unresolved symbol in .../lib/perl5/5.8.0/alpha\-dec_osf/auto/IO/IO.so: sockatmark at .../lib/perl5/5.8.0/alpha\-dec_osf/XSLoader.pm line 75. |
| 221 |
.Ve |
| 222 |
.PP |
| 223 |
you need to either recompile your Perl in Tru64 4.0D or upgrade your |
| 224 |
Tru64 4.0D to at least 4.0F: the \fBsockatmark()\fR system call was |
| 225 |
added in Tru64 4.0F, and the IO extension refers that symbol. |
| 226 |
.SH "read_cur_obj_info: bad file magic number" |
| 227 |
.IX Header "read_cur_obj_info: bad file magic number" |
| 228 |
You may be mixing the Tru64 cc/ar/ld with the GNU gcc/ar/ld. |
| 229 |
That may work, but sometimes it doesn't (your gcc or GNU utils |
| 230 |
may have been compiled for an incompatible OS release). |
| 231 |
.PP |
| 232 |
Try 'which ld' and 'which ld' (or try 'ar \-\-version' and 'ld \-\-version', |
| 233 |
which work only for the GNU tools, and will announce themselves to be such), |
| 234 |
and adjust your PATH so that you are consistently using either |
| 235 |
the native tools or the GNU tools. After fixing your PATH, you should |
| 236 |
do 'make distclean' and start all the way from running the Configure |
| 237 |
since you may have quite a confused situation. |
| 238 |
.SH AUTHOR |
| 239 |
.IX Header "AUTHOR" |
| 240 |
Jarkko Hietaniemi <[email protected]> |