1PERLTRU64(1) Perl Programmers Reference Guide PERLTRU64(1)
2
6 README.tru64 - Perl version 5 on Tru64 (formerly known as Digital UNIX
7 formerly known as DEC OSF/1) systems
8
10 This document describes various features of HP's (formerly Compaq's,
11 formerly Digital's) Unix operating system (Tru64) that will affect how
12 Perl version 5 (hereafter just Perl) is configured, compiled and/or
13 runs.
14 Compiling Perl 5 on Tru64
16 The recommended compiler to use in Tru64 is the native C compiler. The
18 native compiler produces much faster code (the speed difference is
19 noticeable: several dozen percentages) and also more correct code: if
20 you are considering using the GNU C compiler you should use at the very
21 least the release of 2.95.3 since all older gcc releases are known to
22 produce broken code when compiling Perl. One manifestation of this
23 brokenness is the lib/sdbm test dumping core; another is many of the
24 op/regexp and op/pat, or ext/Storable tests dumping core (the exact
25 pattern of failures depending on the GCC release and optimization
26 flags).
27 gcc 3.2.1 is known to work okay with Perl 5.8.0. However, when opti‐
29 mizing the toke.c gcc likes to have a lot of memory, 256 megabytes
30 seems to be enough. The default setting of the process data section in
31 Tru64 should be one gigabyte, but some sites/setups might have lowered
32 that. The configuration process of Perl checks for too low process
33 limits, and lowers the optimization for the toke.c if necessary, and
34 also gives advice on how to raise the process limits.
35 Using Large Files with Perl on Tru64
37 In Tru64 Perl is automatically able to use large files, that is, files
39 larger than 2 gigabytes, there is no need to use the Configure -Duse‐
40 largefiles option as described in INSTALL (though using the option is
41 harmless).
42 Threaded Perl on Tru64
44 If you want to use threads, you should primarily use the new Perl 5.8.0
46 threads model by running Configure with -Duseithreads.
47 The old Perl 5.005 threads is obsolete, unmaintained, and its use is
49 discouraged. If you really want it, run Configure with the
50 -Dusethreads -Duse5005threads options as described in INSTALL.
51 Either thread model is going to work only in Tru64 4.0 and newer
53 releases, older operating releases like 3.2 aren't probably going to
54 work properly with threads.
55 In Tru64 V5 (at least V5.1A, V5.1B) you cannot build threaded Perl with
57 gcc because the system header <pthread.h> explicitly checks for sup‐
58 ported C compilers, gcc (at least 3.2.2) not being one of them. But
59 the system C compiler should work just fine.
60 Long Doubles on Tru64
62 You cannot Configure Perl to use long doubles unless you have at least
64 Tru64 V5.0, the long double support simply wasn't functional enough
65 before that. Perl's Configure will override attempts to use the long
66 doubles (you can notice this by Configure finding out that the modfl()
67 function does not work as it should).
68 At the time of this writing (June 2002), there is a known bug in the
70 Tru64 libc printing of long doubles when not using "e" notation. The
71 values are correct and usable, but you only get a limited number of
72 digits displayed unless you force the issue by using "printf
73 "%.33e",$num" or the like. For Tru64 versions V5.0A through V5.1A, a
74 patch is expected sometime after perl 5.8.0 is released. If your libc
75 has not yet been patched, you'll get a warning from Configure when
76 selecting long doubles.
77 DB_File tests failing on Tru64
79 The DB_File tests (db-btree.t, db-hash.t, db-recno.t) may fail you have
81 installed a newer version of Berkeley DB into the system and the -I and
82 -L compiler and linker flags introduce version conflicts with the DB
83 1.85 headers and libraries that came with the Tru64. For example, mix‐
84 ing a DB v2 library with the DB v1 headers is a bad idea. Watch out
85 for Configure options -Dlocincpth and -Dloclibpth, and check your
86 /usr/local/include and /usr/local/lib since they are included by
87 default.
88 The second option is to explicitly instruct Configure to detect the
90 newer Berkeley DB installation, by supplying the right directories with
91 "-Dlocincpth=/some/include" and "-Dloclibpth=/some/lib" and before run‐
92 ning "make test" setting your LD_LIBRARY_PATH to /some/lib.
93 The third option is to work around the problem by disabling the DB_File
95 completely when build Perl by specifying -Ui_db to Configure, and then
96 using the BerkeleyDB module from CPAN instead of DB_File. The Berke‐
97 leyDB works with Berkeley DB versions 2.* or greater.
98 The Berkeley DB 4.1.25 has been tested with Tru64 V5.1A and found to
100 work. The latest Berkeley DB can be found from http://www.sleepy‐
101 cat.com.
102 64-bit Perl on Tru64
104 In Tru64 Perl's integers are automatically 64-bit wide, there is no
106 need to use the Configure -Duse64bitint option as described in INSTALL.
107 Similarly, there is no need for -Duse64bitall since pointers are auto‐
108 matically 64-bit wide.
109 Warnings about floating-point overflow when compiling Perl on Tru64
111 When compiling Perl in Tru64 you may (depending on the compiler
113 release) see two warnings like this
114 cc: Warning: numeric.c, line 104: In this statement, floating-point overflow occurs in evaluating the expression "1.8e308". (floatoverfl)
116 return HUGE_VAL;
117 -----------^
118 and when compiling the POSIX extension
120 cc: Warning: const-c.inc, line 2007: In this statement, floating-point overflow occurs in evaluating the expression "1.8e308". (floatoverfl)
122 return HUGE_VAL;
123 -------------------^
124 The exact line numbers may vary between Perl releases. The warnings
126 are benign and can be ignored: in later C compiler releases the warn‐
127 ings should be gone.
128 When the file pp_sys.c is being compiled you may (depending on the
130 operating system release) see an additional compiler flag being used:
131 "-DNO_EFF_ONLY_OK". This is normal and refers to a feature that is
132 relevant only if you use the "filetest" pragma. In older releases of
133 the operating system the feature was broken and the NO_EFF_ONLY_OK
134 instructs Perl not to use the feature.
135
137 During "make test" the "comp/cpp" will be skipped because on Tru64 it
138 cannot be tested before Perl has been installed. The test refers to
139 the use of the "-P" option of Perl.
140
142 The ext/ODBM_File/odbm is known to fail with static builds (Configure
143 -Uusedl) due to a known bug in Tru64's static libdbm library. The good
144 news is that you very probably don't need to ever use the ODBM_File
145 extension since more advanced NDBM_File works fine, not to mention the
146 even more advanced DB_File.
147
149 If you get an error like
150 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.
152 you need to either recompile your Perl in Tru64 4.0D or upgrade your
154 Tru64 4.0D to at least 4.0F: the sockatmark() system call was added in
155 Tru64 4.0F, and the IO extension refers that symbol.
156
158 Jarkko Hietaniemi <jhi@iki.fi>
159perl v5.8.8 2006-01-07 PERLTRU64(1)