Commit | Line | Data |
---|---|---|
ea3bceb2 JH |
1 | If you read this file _as_is_, just ignore the funny characters you see. |
2 | It is written in the POD format (see pod/perlpod.pod) which is specially | |
3 | designed to be readable as is. | |
4 | ||
5 | =head1 NAME | |
6 | ||
7 | README.tru64 - Perl version 5 on Tru64 (formerly known as Digital UNIX formerly known as DEC OSF/1) systems | |
8 | ||
9 | =head1 DESCRIPTION | |
10 | ||
11 | This document describes various features of Compaq's (formerly Digital's) | |
12 | Unix operating system (Tru64) that will affect how Perl version 5 | |
13 | is compiled and/or runs. | |
14 | ||
15 | =head2 Compiling Perl 5 on Tru64 | |
16 | ||
17 | The recommended compiler to use in Tru64 is the native C compiler. | |
18 | The native compiler produces much faster code (the speed difference is | |
19 | noticeable: several dozen percentages) and also more correct code: if you | |
20 | are considering using the GNU C compiler you should use the gcc 2.95.3 | |
21 | release since older gcc releases are known to produce buggy code when | |
22 | compiling Perl. | |
23 | ||
24 | =head2 Using Large Files with Perl on Tru64 | |
25 | ||
26 | In Tru64 Perl is automatically able to use large files, that is, files | |
27 | larger than 2 gigabytes, there is no need to use the Configure | |
28 | -Duselargefiles option as described in INSTALL. | |
29 | ||
30 | =head2 Threaded Perl on Tru64 | |
31 | ||
32 | To compile Perl to use the old Perl 5.005 threads model, run Configure | |
33 | with the -Dusethreads -Duse5005threads options as described in INSTALL. | |
34 | This will probably only work in Tru64 4.0 and newer releases, older | |
35 | operating releases like 3.2 aren't probably going to work properly | |
36 | with threads. | |
37 | ||
38 | Beware: the Perl 5.005 threads model is known to have bugs, for | |
39 | example the regular expressions are not thread-safe. The bugs are | |
40 | very hard to fix are and therefore the 5.005 threads model is still | |
41 | classified as an experimental feature. | |
42 | ||
43 | =head2 64-bit Perl on Tru64 | |
44 | ||
45 | In Tru64 Perl's integers are automatically 64-bit wide, there is | |
46 | no need to use the Configure -Duse64bitint option as described | |
47 | in INSTALL. Similarly, there is no need for -Duse64bitall. | |
48 | ||
49 | =head2 Warnings about floating-point overflow when compiling Perl on Tru64 | |
50 | ||
51 | When compiling Perl in Tru64 you may (depending on the compiler | |
52 | release) see two warnings like this | |
53 | ||
54 | cc: Warning: util.c, line 3797: In this statement, floating-point overflow occurs in evaluating the expression "1.8e308". (floatoverfl) | |
55 | return HUGE_VAL; | |
56 | -----------^ | |
57 | ||
58 | cc: Warning: POSIX.xs, line 1304: In this statement, floating-point overflow occurs in evaluating the expression "1.8e308". (floatoverfl) | |
59 | return HUGE_VAL; | |
60 | -------------------^ | |
61 | ||
62 | The exact line numbers may vary between Perl releases. | |
63 | The warnings are benign and can be ignored. | |
64 | ||
65 | When the file F<pp_sys.c> is being compiled you may (depending on the | |
66 | operating system release) see an additional compiler flag being used: | |
67 | C<-DNO_EFF_ONLY_OK>. This is normal and refers to a feature that is | |
68 | relevant only if you use the C<filetest> pragma. In older releases of | |
69 | the operating system the feature was broken and the NO_EFF_ONLY_OK | |
70 | instructs Perl not to use the feature. | |
71 | ||
72 | =head1 Testing Perl on Tru64 | |
73 | ||
74 | During "make test" the C<comp/cpp> will be skipped because on Tru64 it | |
75 | cannot be tested before Perl has been installed. The test refers to | |
76 | the use of the C<-P> option of Perl. | |
77 | ||
78 | =head1 AUTHOR | |
79 | ||
80 | Jarkko Hietaniemi <jhi@iki.fi> | |
81 | ||
82 | =cut |