Commit | Line | Data |
ea3bceb2 |
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 | |
88ec1f5d |
11 | This document describes various features of HP's (formerly Compaq's, |
12 | formerly Digital's) Unix operating system (Tru64) that will affect |
92c48b5b |
13 | how Perl version 5 (hereafter just Perl) is configured, compiled |
14 | and/or runs. |
ea3bceb2 |
15 | |
16 | =head2 Compiling Perl 5 on Tru64 |
17 | |
18 | The recommended compiler to use in Tru64 is the native C compiler. |
88ec1f5d |
19 | The native compiler produces much faster code (the speed difference is |
20 | noticeable: several dozen percentages) and also more correct code: if |
92c48b5b |
21 | you are considering using the GNU C compiler you should use at the |
22 | very least the release of 2.95.3 since all older gcc releases are |
23 | known to produce broken code when compiling Perl. One manifestation |
24 | of this brokenness is the lib/sdbm test dumping core; another is many |
25 | of the op/regexp and op/pat, or ext/Storable tests dumping core |
26 | (the exact pattern of failures depending on the GCC release and |
27 | optimization flags). |
ea3bceb2 |
28 | |
29 | =head2 Using Large Files with Perl on Tru64 |
30 | |
88ec1f5d |
31 | In Tru64 Perl is automatically able to use large files, that is, |
32 | files larger than 2 gigabytes, there is no need to use the Configure |
92c48b5b |
33 | -Duselargefiles option as described in INSTALL (though using the option |
34 | is harmless). |
ea3bceb2 |
35 | |
36 | =head2 Threaded Perl on Tru64 |
37 | |
294f22c5 |
38 | If you want to use threads, you should primarily use the Perl |
88ec1f5d |
39 | 5.8.0 threads model by running Configure with -Duseithreads. |
ea3bceb2 |
40 | |
294f22c5 |
41 | Perl threading is going to work only in Tru64 4.0 and newer releases, |
42 | older operating releases like 3.2 aren't probably going to work |
43 | properly with threads. |
ea3bceb2 |
44 | |
bef5f079 |
45 | =head2 Long Doubles on Tru64 |
46 | |
92c48b5b |
47 | You cannot Configure Perl to use long doubles unless you have at least |
48 | Tru64 V5.0, the long double support simply wasn't functional enough |
49 | before that. Perl's Configure will override attempts to use the long |
50 | doubles (you can notice this by Configure finding out that the modfl() |
51 | function does not work as it should). |
bef5f079 |
52 | |
88ec1f5d |
53 | At the time of this writing (June 2002), there is a known bug in the |
54 | Tru64 libc printing of long doubles when not using "e" notation. |
55 | The values are correct and usable, but you only get a limited number |
56 | of digits displayed unless you force the issue by using C<printf |
57 | "%.33e",$num> or the like. For Tru64 versions V5.0A through V5.1A, a |
58 | patch is expected sometime after perl 5.8.0 is released. If your libc |
59 | has not yet been patched, you'll get a warning from Configure when |
60 | selecting long doubles. |
fa17d112 |
61 | |
cfc8a802 |
62 | =head2 db-hash.t failing on Tru64 |
63 | |
64 | The Berkeley DB 1.85 coming with the Tru64 is unfortunately buggy. |
65 | In general in Tru64 V4.* it seemed to be more stable, but in V5.* |
66 | something broke (even though the DB stayed at release 1.85) and |
67 | the DB_File extension test db-hash.t may fail by dumping core after |
68 | the subtest 21. There really is no good cure as of Tru64 V5.1A expect |
69 | installing a newer Berkeley DB and supplying the right directories for |
70 | -Dlocincpth=/some/include and -Dloclibpth=/some/lib when running Configure. |
71 | |
72 | You can also work around the problem by disabling the DB_File by |
73 | specifying -Ui_db to Configure, and then using the BerkeleyFile module |
74 | from CPAN instead of DB_File. The BerkeleyFile works with Berkeley DB |
75 | versions 2.* or greater. |
76 | |
77 | The Berkeley DB 4.0.14 has been tested with Tru64 V5.1A and found |
78 | to work. The latest Berkeley DB can be found from F<http://www.sleepycat.com>. |
79 | |
ea3bceb2 |
80 | =head2 64-bit Perl on Tru64 |
81 | |
82 | In Tru64 Perl's integers are automatically 64-bit wide, there is |
83 | no need to use the Configure -Duse64bitint option as described |
88ec1f5d |
84 | in INSTALL. Similarly, there is no need for -Duse64bitall |
85 | since pointers are automatically 64-bit wide. |
ea3bceb2 |
86 | |
87 | =head2 Warnings about floating-point overflow when compiling Perl on Tru64 |
88 | |
89 | When compiling Perl in Tru64 you may (depending on the compiler |
90 | release) see two warnings like this |
91 | |
d780cd7a |
92 | cc: Warning: numeric.c, line 104: In this statement, floating-point overflow occurs in evaluating the expression "1.8e308". (floatoverfl) |
ea3bceb2 |
93 | return HUGE_VAL; |
94 | -----------^ |
95 | |
ef3337d4 |
96 | and when compiling the POSIX extension |
97 | |
98 | cc: Warning: const-c.inc, line 2007: In this statement, floating-point overflow occurs in evaluating the expression "1.8e308". (floatoverfl) |
ea3bceb2 |
99 | return HUGE_VAL; |
100 | -------------------^ |
101 | |
92c48b5b |
102 | The exact line numbers may vary between Perl releases. The warnings |
103 | are benign and can be ignored: in later C compiler releases the warnings |
104 | should be gone. |
ea3bceb2 |
105 | |
106 | When the file F<pp_sys.c> is being compiled you may (depending on the |
107 | operating system release) see an additional compiler flag being used: |
108 | C<-DNO_EFF_ONLY_OK>. This is normal and refers to a feature that is |
109 | relevant only if you use the C<filetest> pragma. In older releases of |
110 | the operating system the feature was broken and the NO_EFF_ONLY_OK |
111 | instructs Perl not to use the feature. |
112 | |
113 | =head1 Testing Perl on Tru64 |
114 | |
115 | During "make test" the C<comp/cpp> will be skipped because on Tru64 it |
116 | cannot be tested before Perl has been installed. The test refers to |
117 | the use of the C<-P> option of Perl. |
118 | |
2dfde39d |
119 | =head1 ext/ODBM_File/odbm Test Failing With Static Builds |
120 | |
121 | The ext/ODBM_File/odbm is known to fail with static builds |
88ec1f5d |
122 | (Configure -Uusedl) due to a known bug in Tru64's static libdbm |
2dfde39d |
123 | library. The good news is that you very probably don't need to ever |
124 | use the ODBM_File extension since more advanced NDBM_File works fine, |
125 | not to mention the even more advanced DB_File. |
126 | |
9a8de003 |
127 | =head1 Perl Fails Because Of Unresolved Symbol sockatmark |
128 | |
129 | If you get an error like |
130 | |
4282de36 |
131 | 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. |
9a8de003 |
132 | |
133 | you need to either recompile your Perl in Tru64 4.0D or upgrade your |
92c48b5b |
134 | Tru64 4.0D to at least 4.0F: the sockatmark() system call was |
135 | added in Tru64 4.0F, and the IO extension refers that symbol. |
9a8de003 |
136 | |
ea3bceb2 |
137 | =head1 AUTHOR |
138 | |
139 | Jarkko Hietaniemi <jhi@iki.fi> |
140 | |
141 | =cut |