Debian Codegraph @

upstream/mageia-cauldron/man1/perltru64.1

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