Commit | Line | Data |
---|---|---|
920dae64 AT |
1 | .\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.32 |
2 | .\" | |
3 | .\" Standard preamble: | |
4 | .\" ======================================================================== | |
5 | .de Sh \" Subsection heading | |
6 | .br | |
7 | .if t .Sp | |
8 | .ne 5 | |
9 | .PP | |
10 | \fB\\$1\fR | |
11 | .PP | |
12 | .. | |
13 | .de Sp \" Vertical space (when we can't use .PP) | |
14 | .if t .sp .5v | |
15 | .if n .sp | |
16 | .. | |
17 | .de Vb \" Begin verbatim text | |
18 | .ft CW | |
19 | .nf | |
20 | .ne \\$1 | |
21 | .. | |
22 | .de Ve \" End verbatim text | |
23 | .ft R | |
24 | .fi | |
25 | .. | |
26 | .\" Set up some character translations and predefined strings. \*(-- will | |
27 | .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left | |
28 | .\" double quote, and \*(R" will give a right double quote. | will give a | |
29 | .\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to | |
30 | .\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C' | |
31 | .\" expand to `' in nroff, nothing in troff, for use with C<>. | |
32 | .tr \(*W-|\(bv\*(Tr | |
33 | .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' | |
34 | .ie n \{\ | |
35 | . ds -- \(*W- | |
36 | . ds PI pi | |
37 | . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch | |
38 | . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch | |
39 | . ds L" "" | |
40 | . ds R" "" | |
41 | . ds C` "" | |
42 | . ds C' "" | |
43 | 'br\} | |
44 | .el\{\ | |
45 | . ds -- \|\(em\| | |
46 | . ds PI \(*p | |
47 | . ds L" `` | |
48 | . ds R" '' | |
49 | 'br\} | |
50 | .\" | |
51 | .\" If the F register is turned on, we'll generate index entries on stderr for | |
52 | .\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index | |
53 | .\" entries marked with X<> in POD. Of course, you'll have to process the | |
54 | .\" output yourself in some meaningful fashion. | |
55 | .if \nF \{\ | |
56 | . de IX | |
57 | . tm Index:\\$1\t\\n%\t"\\$2" | |
58 | .. | |
59 | . nr % 0 | |
60 | . rr F | |
61 | .\} | |
62 | .\" | |
63 | .\" For nroff, turn off justification. Always turn off hyphenation; it makes | |
64 | .\" way too many mistakes in technical documents. | |
65 | .hy 0 | |
66 | .if n .na | |
67 | .\" | |
68 | .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). | |
69 | .\" Fear. Run. Save yourself. No user-serviceable parts. | |
70 | . \" fudge factors for nroff and troff | |
71 | .if n \{\ | |
72 | . ds #H 0 | |
73 | . ds #V .8m | |
74 | . ds #F .3m | |
75 | . ds #[ \f1 | |
76 | . ds #] \fP | |
77 | .\} | |
78 | .if t \{\ | |
79 | . ds #H ((1u-(\\\\n(.fu%2u))*.13m) | |
80 | . ds #V .6m | |
81 | . ds #F 0 | |
82 | . ds #[ \& | |
83 | . ds #] \& | |
84 | .\} | |
85 | . \" simple accents for nroff and troff | |
86 | .if n \{\ | |
87 | . ds ' \& | |
88 | . ds ` \& | |
89 | . ds ^ \& | |
90 | . ds , \& | |
91 | . ds ~ ~ | |
92 | . ds / | |
93 | .\} | |
94 | .if t \{\ | |
95 | . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" | |
96 | . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' | |
97 | . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' | |
98 | . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' | |
99 | . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' | |
100 | . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' | |
101 | .\} | |
102 | . \" troff and (daisy-wheel) nroff accents | |
103 | .ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V' | |
104 | .ds 8 \h'\*(#H'\(*b\h'-\*(#H' | |
105 | .ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#] | |
106 | .ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H' | |
107 | .ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u' | |
108 | .ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#] | |
109 | .ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#] | |
110 | .ds ae a\h'-(\w'a'u*4/10)'e | |
111 | .ds Ae A\h'-(\w'A'u*4/10)'E | |
112 | . \" corrections for vroff | |
113 | .if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u' | |
114 | .if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u' | |
115 | . \" for low resolution devices (crt and lpr) | |
116 | .if \n(.H>23 .if \n(.V>19 \ | |
117 | \{\ | |
118 | . ds : e | |
119 | . ds 8 ss | |
120 | . ds o a | |
121 | . ds d- d\h'-1'\(ga | |
122 | . ds D- D\h'-1'\(hy | |
123 | . ds th \o'bp' | |
124 | . ds Th \o'LP' | |
125 | . ds ae ae | |
126 | . ds Ae AE | |
127 | .\} | |
128 | .rm #[ #] #H #V #F C | |
129 | .\" ======================================================================== | |
130 | .\" | |
131 | .IX Title "PERLTRU64 1" | |
132 | .TH PERLTRU64 1 "2006-01-07" "perl v5.8.8" "Perl Programmers Reference Guide" | |
133 | .SH "NAME" | |
134 | README.tru64 \- Perl version 5 on Tru64 (formerly known as Digital UNIX formerly known as DEC OSF/1) systems | |
135 | .SH "DESCRIPTION" | |
136 | .IX Header "DESCRIPTION" | |
137 | This document describes various features of \s-1HP\s0's (formerly Compaq's, | |
138 | formerly Digital's) Unix operating system (Tru64) that will affect | |
139 | how Perl version 5 (hereafter just Perl) is configured, compiled | |
140 | and/or runs. | |
141 | .Sh "Compiling Perl 5 on Tru64" | |
142 | .IX Subsection "Compiling Perl 5 on Tru64" | |
143 | The recommended compiler to use in Tru64 is the native C compiler. | |
144 | The native compiler produces much faster code (the speed difference is | |
145 | noticeable: several dozen percentages) and also more correct code: if | |
146 | you are considering using the \s-1GNU\s0 C compiler you should use at the | |
147 | very least the release of 2.95.3 since all older gcc releases are | |
148 | known to produce broken code when compiling Perl. One manifestation | |
149 | of this brokenness is the lib/sdbm test dumping core; another is many | |
150 | of the op/regexp and op/pat, or ext/Storable tests dumping core | |
151 | (the exact pattern of failures depending on the \s-1GCC\s0 release and | |
152 | optimization flags). | |
153 | .PP | |
154 | gcc 3.2.1 is known to work okay with Perl 5.8.0. However, when | |
155 | optimizing the toke.c gcc likes to have a lot of memory, 256 megabytes | |
156 | seems to be enough. The default setting of the process data section | |
157 | in Tru64 should be one gigabyte, but some sites/setups might have | |
158 | lowered that. The configuration process of Perl checks for too low | |
159 | process limits, and lowers the optimization for the toke.c if | |
160 | necessary, and also gives advice on how to raise the process limits. | |
161 | .Sh "Using Large Files with Perl on Tru64" | |
162 | .IX Subsection "Using Large Files with Perl on Tru64" | |
163 | In Tru64 Perl is automatically able to use large files, that is, | |
164 | files larger than 2 gigabytes, there is no need to use the Configure | |
165 | \&\-Duselargefiles option as described in \s-1INSTALL\s0 (though using the option | |
166 | is harmless). | |
167 | .Sh "Threaded Perl on Tru64" | |
168 | .IX Subsection "Threaded Perl on Tru64" | |
169 | If you want to use threads, you should primarily use the new Perl | |
170 | 5.8.0 threads model by running Configure with \-Duseithreads. | |
171 | .PP | |
172 | The old Perl 5.005 threads is obsolete, unmaintained, and its use is | |
173 | discouraged. If you really want it, run Configure with the | |
174 | \&\-Dusethreads \-Duse5005threads options as described in \s-1INSTALL\s0. | |
175 | .PP | |
176 | Either thread model is going to work only in Tru64 4.0 and newer | |
177 | releases, older operating releases like 3.2 aren't probably going | |
178 | to work properly with threads. | |
179 | .PP | |
180 | In Tru64 V5 (at least V5.1A, V5.1B) you cannot build threaded Perl with gcc | |
181 | because the system header <pthread.h> explicitly checks for supported | |
182 | C compilers, gcc (at least 3.2.2) not being one of them. But the | |
183 | system C compiler should work just fine. | |
184 | .Sh "Long Doubles on Tru64" | |
185 | .IX Subsection "Long Doubles on Tru64" | |
186 | You cannot Configure Perl to use long doubles unless you have at least | |
187 | Tru64 V5.0, the long double support simply wasn't functional enough | |
188 | before that. Perl's Configure will override attempts to use the long | |
189 | doubles (you can notice this by Configure finding out that the \fImodfl()\fR | |
190 | function does not work as it should). | |
191 | .PP | |
192 | At the time of this writing (June 2002), there is a known bug in the | |
193 | Tru64 libc printing of long doubles when not using \*(L"e\*(R" notation. | |
194 | The values are correct and usable, but you only get a limited number | |
195 | of digits displayed unless you force the issue by using \f(CW\*(C`printf | |
196 | "%.33e",$num\*(C'\fR or the like. For Tru64 versions V5.0A through V5.1A, a | |
197 | patch is expected sometime after perl 5.8.0 is released. If your libc | |
198 | has not yet been patched, you'll get a warning from Configure when | |
199 | selecting long doubles. | |
200 | .Sh "DB_File tests failing on Tru64" | |
201 | .IX Subsection "DB_File tests failing on Tru64" | |
202 | The DB_File tests (db\-btree.t, db\-hash.t, db\-recno.t) may fail you | |
203 | have installed a newer version of Berkeley \s-1DB\s0 into the system and the | |
204 | \&\-I and \-L compiler and linker flags introduce version conflicts with | |
205 | the \s-1DB\s0 1.85 headers and libraries that came with the Tru64. For example, | |
206 | mixing a \s-1DB\s0 v2 library with the \s-1DB\s0 v1 headers is a bad idea. Watch | |
207 | out for Configure options \-Dlocincpth and \-Dloclibpth, and check your | |
208 | /usr/local/include and /usr/local/lib since they are included by default. | |
209 | .PP | |
210 | The second option is to explicitly instruct Configure to detect the | |
211 | newer Berkeley \s-1DB\s0 installation, by supplying the right directories with | |
212 | \&\f(CW\*(C`\-Dlocincpth=/some/include\*(C'\fR and \f(CW\*(C`\-Dloclibpth=/some/lib\*(C'\fR \fBand\fR before | |
213 | running \*(L"make test\*(R" setting your \s-1LD_LIBRARY_PATH\s0 to \fI/some/lib\fR. | |
214 | .PP | |
215 | The third option is to work around the problem by disabling the | |
216 | DB_File completely when build Perl by specifying \-Ui_db to Configure, | |
217 | and then using the BerkeleyDB module from \s-1CPAN\s0 instead of DB_File. | |
218 | The BerkeleyDB works with Berkeley \s-1DB\s0 versions 2.* or greater. | |
219 | .PP | |
220 | The Berkeley \s-1DB\s0 4.1.25 has been tested with Tru64 V5.1A and found | |
221 | to work. The latest Berkeley \s-1DB\s0 can be found from \fIhttp://www.sleepycat.com\fR. | |
222 | .Sh "64\-bit Perl on Tru64" | |
223 | .IX Subsection "64-bit Perl on Tru64" | |
224 | In Tru64 Perl's integers are automatically 64\-bit wide, there is | |
225 | no need to use the Configure \-Duse64bitint option as described | |
226 | in \s-1INSTALL\s0. Similarly, there is no need for \-Duse64bitall | |
227 | since pointers are automatically 64\-bit wide. | |
228 | .Sh "Warnings about floating-point overflow when compiling Perl on Tru64" | |
229 | .IX Subsection "Warnings about floating-point overflow when compiling Perl on Tru64" | |
230 | When compiling Perl in Tru64 you may (depending on the compiler | |
231 | release) see two warnings like this | |
232 | .PP | |
233 | .Vb 3 | |
234 | \& cc: Warning: numeric.c, line 104: In this statement, floating-point overflow occurs in evaluating the expression "1.8e308". (floatoverfl) | |
235 | \& return HUGE_VAL; | |
236 | \& -----------^ | |
237 | .Ve | |
238 | .PP | |
239 | and when compiling the \s-1POSIX\s0 extension | |
240 | .PP | |
241 | .Vb 3 | |
242 | \& cc: Warning: const-c.inc, line 2007: In this statement, floating-point overflow occurs in evaluating the expression "1.8e308". (floatoverfl) | |
243 | \& return HUGE_VAL; | |
244 | \& -------------------^ | |
245 | .Ve | |
246 | .PP | |
247 | The exact line numbers may vary between Perl releases. The warnings | |
248 | are benign and can be ignored: in later C compiler releases the warnings | |
249 | should be gone. | |
250 | .PP | |
251 | When the file \fIpp_sys.c\fR is being compiled you may (depending on the | |
252 | operating system release) see an additional compiler flag being used: | |
253 | \&\f(CW\*(C`\-DNO_EFF_ONLY_OK\*(C'\fR. This is normal and refers to a feature that is | |
254 | relevant only if you use the \f(CW\*(C`filetest\*(C'\fR pragma. In older releases of | |
255 | the operating system the feature was broken and the \s-1NO_EFF_ONLY_OK\s0 | |
256 | instructs Perl not to use the feature. | |
257 | .SH "Testing Perl on Tru64" | |
258 | .IX Header "Testing Perl on Tru64" | |
259 | During \*(L"make test\*(R" the \f(CW\*(C`comp/cpp\*(C'\fR will be skipped because on Tru64 it | |
260 | cannot be tested before Perl has been installed. The test refers to | |
261 | the use of the \f(CW\*(C`\-P\*(C'\fR option of Perl. | |
262 | .SH "ext/ODBM_File/odbm Test Failing With Static Builds" | |
263 | .IX Header "ext/ODBM_File/odbm Test Failing With Static Builds" | |
264 | The ext/ODBM_File/odbm is known to fail with static builds | |
265 | (Configure \-Uusedl) due to a known bug in Tru64's static libdbm | |
266 | library. The good news is that you very probably don't need to ever | |
267 | use the ODBM_File extension since more advanced NDBM_File works fine, | |
268 | not to mention the even more advanced DB_File. | |
269 | .SH "Perl Fails Because Of Unresolved Symbol sockatmark" | |
270 | .IX Header "Perl Fails Because Of Unresolved Symbol sockatmark" | |
271 | If you get an error like | |
272 | .PP | |
273 | .Vb 1 | |
274 | \& Can't load '.../OSF1/lib/perl5/5.8.0/alpha-dec_osf/auto/IO/IO.so' 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. | |
275 | .Ve | |
276 | .PP | |
277 | you need to either recompile your Perl in Tru64 4.0D or upgrade your | |
278 | Tru64 4.0D to at least 4.0F: the \fIsockatmark()\fR system call was | |
279 | added in Tru64 4.0F, and the \s-1IO\s0 extension refers that symbol. | |
280 | .SH "AUTHOR" | |
281 | .IX Header "AUTHOR" | |
282 | Jarkko Hietaniemi <jhi@iki.fi> |