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
17 native compiler produces much faster code (the speed difference is
18 noticeable: several dozen percentages) and also more correct code: if
19 you are considering using the GNU C compiler you should use at the very
20 least the release of 2.95.3 since all older gcc releases are known to
21 produce broken code when compiling Perl. One manifestation of this
22 brokenness is the lib/sdbm test dumping core; another is many of the
23 op/regexp and op/pat, or ext/Storable tests dumping core (the exact
24 pattern of failures depending on the GCC release and optimization
25 flags).
26 gcc 3.2.1 is known to work okay with Perl 5.8.0. However, when
28 optimizing the toke.c gcc likes to have a lot of memory, 256 megabytes
29 seems to be enough. The default setting of the process data section in
30 Tru64 should be one gigabyte, but some sites/setups might have lowered
31 that. The configuration process of Perl checks for too low process
32 limits, and lowers the optimization for the toke.c if necessary, and
33 also gives advice on how to raise the process limits.
34 Also, Configure might abort with
36 Build a threading Perl? [n]
38 Configure[2437]: Syntax error at line 1 : `config.sh' is not expected.
39 This indicates that Configure is being run with a broken Korn shell
41 (even though you think you are using a Bourne shell by using "sh
42 Configure" or "./Configure"). The Korn shell bug has been reported to
43 Compaq as of February 1999 but in the meanwhile, the reason ksh is
44 being used is that you have the environment variable BIN_SH set to
45 'xpg4'. This causes /bin/sh to delegate its duties to /bin/posix/sh (a
46 ksh). Unset the environment variable and rerun Configure.
47 Using Large Files with Perl on Tru64
49 In Tru64 Perl is automatically able to use large files, that is, files
50 larger than 2 gigabytes, there is no need to use the Configure
51 -Duselargefiles option as described in INSTALL (though using the option
52 is harmless).
53 Threaded Perl on Tru64
55 If you want to use threads, you should primarily use the Perl 5.8.0
56 threads model by running Configure with -Duseithreads.
57 Perl threading is going to work only in Tru64 4.0 and newer releases,
59 older operating releases like 3.2 aren't probably going to work
60 properly with threads.
61 In Tru64 V5 (at least V5.1A, V5.1B) you cannot build threaded Perl with
63 gcc because the system header <pthread.h> explicitly checks for
64 supported C compilers, gcc (at least 3.2.2) not being one of them. But
65 the system C compiler should work just fine.
66 Long Doubles on Tru64
68 You cannot Configure Perl to use long doubles unless you have at least
69 Tru64 V5.0, the long double support simply wasn't functional enough
70 before that. Perl's Configure will override attempts to use the long
71 doubles (you can notice this by Configure finding out that the modfl()
72 function does not work as it should).
73 At the time of this writing (June 2002), there is a known bug in the
75 Tru64 libc printing of long doubles when not using "e" notation. The
76 values are correct and usable, but you only get a limited number of
77 digits displayed unless you force the issue by using "printf
78 "%.33e",$num" or the like. For Tru64 versions V5.0A through V5.1A, a
79 patch is expected sometime after perl 5.8.0 is released. If your libc
80 has not yet been patched, you'll get a warning from Configure when
81 selecting long doubles.
82 DB_File tests failing on Tru64
84 The DB_File tests (db-btree.t, db-hash.t, db-recno.t) may fail you have
85 installed a newer version of Berkeley DB into the system and the -I and
86 -L compiler and linker flags introduce version conflicts with the DB
87 1.85 headers and libraries that came with the Tru64. For example,
88 mixing a DB v2 library with the DB v1 headers is a bad idea. Watch out
89 for Configure options -Dlocincpth and -Dloclibpth, and check your
90 /usr/local/include and /usr/local/lib since they are included by
91 default.
92 The second option is to explicitly instruct Configure to detect the
94 newer Berkeley DB installation, by supplying the right directories with
95 "-Dlocincpth=/some/include" and "-Dloclibpth=/some/lib" and before
96 running "make test" setting your LD_LIBRARY_PATH to /some/lib.
97 The third option is to work around the problem by disabling the DB_File
99 completely when build Perl by specifying -Ui_db to Configure, and then
100 using the BerkeleyDB module from CPAN instead of DB_File. The
101 BerkeleyDB works with Berkeley DB versions 2.* or greater.
102 The Berkeley DB 4.1.25 has been tested with Tru64 V5.1A and found to
104 work. The latest Berkeley DB can be found from
105 http://www.sleepycat.com.
106 64-bit Perl on Tru64
108 In Tru64 Perl's integers are automatically 64-bit wide, there is no
109 need to use the Configure -Duse64bitint option as described in INSTALL.
110 Similarly, there is no need for -Duse64bitall since pointers are
111 automatically 64-bit wide.
112 Warnings about floating-point overflow when compiling Perl on Tru64
114 When compiling Perl in Tru64 you may (depending on the compiler
115 release) see two warnings like this
116 cc: Warning: numeric.c, line 104: In this statement, floating-point overflow occurs in evaluating the expression "1.8e308". (floatoverfl)
118 return HUGE_VAL;
119 -----------^
120 and when compiling the POSIX extension
122 cc: Warning: const-c.inc, line 2007: In this statement, floating-point overflow occurs in evaluating the expression "1.8e308". (floatoverfl)
124 return HUGE_VAL;
125 -------------------^
126 The exact line numbers may vary between Perl releases. The warnings
128 are benign and can be ignored: in later C compiler releases the
129 warnings should be gone.
130 When the file pp_sys.c is being compiled you may (depending on the
132 operating system release) see an additional compiler flag being used:
133 "-DNO_EFF_ONLY_OK". This is normal and refers to a feature that is
134 relevant only if you use the "filetest" pragma. In older releases of
135 the operating system the feature was broken and the NO_EFF_ONLY_OK
136 instructs Perl not to use the feature.
137
139 During "make test" the "comp/cpp" will be skipped because on Tru64 it
140 cannot be tested before Perl has been installed. The test refers to
141 the use of the "-P" option of Perl.
142
144 The ext/ODBM_File/odbm is known to fail with static builds (Configure
145 -Uusedl) due to a known bug in Tru64's static libdbm library. The good
146 news is that you very probably don't need to ever use the ODBM_File
147 extension since more advanced NDBM_File works fine, not to mention the
148 even more advanced DB_File.
149
151 If you get an error like
152 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.
154 you need to either recompile your Perl in Tru64 4.0D or upgrade your
156 Tru64 4.0D to at least 4.0F: the sockatmark() system call was added in
157 Tru64 4.0F, and the IO extension refers that symbol.
158
160 Jarkko Hietaniemi <jhi@iki.fi>
161perl v5.10.1 2009-02-12 PERLTRU64(1)