mingw/html/pod/perltru64.html

   1 <?xml version="1.0" ?>
   2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml">
   4 <head>
   5 <title>README.tru64 - Perl version 5 on Tru64 systems</title>
   6 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
   7 <link rev="made" href="mailto:" />
   8 </head>
   9
  10 <body style="background-color: white">
  11 <table border="0" width="100%" cellspacing="0" cellpadding="3">
  12 <tr><td class="block" style="background-color: #cccccc" valign="middle">
  13 <big><strong><span class="block">&nbsp;README.tru64 - Perl version 5 on Tru64 systems</span></strong></big>
  14 </td></tr>
  15 </table>
  16
  17 <p><a name="__index__"></a></p>
  18 <!-- INDEX BEGIN -->
  19
  20 <ul>
  21
  22         <li><a href="#name">NAME</a></li>
  23         <li><a href="#description">DESCRIPTION</a></li>
  24         <ul>
  25
  26                 <li><a href="#compiling_perl_5_on_tru64">Compiling Perl 5 on Tru64</a></li>
  27                 <li><a href="#using_large_files_with_perl_on_tru64">Using Large Files with Perl on Tru64</a></li>
  28                 <li><a href="#threaded_perl_on_tru64">Threaded Perl on Tru64</a></li>
  29                 <li><a href="#long_doubles_on_tru64">Long Doubles on Tru64</a></li>
  30                 <li><a href="#db_file_tests_failing_on_tru64">DB_File tests failing on Tru64</a></li>
  31                 <li><a href="#64bit_perl_on_tru64">64-bit Perl on Tru64</a></li>
  32                 <li><a href="#warnings_about_floatingpoint_overflow_when_compiling_perl_on_tru64">Warnings about floating-point overflow when compiling Perl on Tru64</a></li>
  33         </ul>
  34
  35         <li><a href="#testing_perl_on_tru64">Testing Perl on Tru64</a></li>
  36         <li><a href="#ext_odbm_file_odbm_test_failing_with_static_builds">ext/ODBM_File/odbm Test Failing With Static Builds</a></li>
  37         <li><a href="#perl_fails_because_of_unresolved_symbol_sockatmark">Perl Fails Because Of Unresolved Symbol sockatmark</a></li>
  38         <li><a href="#author">AUTHOR</a></li>
  39 </ul>
  40 <!-- INDEX END -->
  41
  42 <hr />
  43 <p>
  44 </p>
  45 <h1><a name="name">NAME</a></h1>
  46 <p>README.tru64 - Perl version 5 on Tru64 (formerly known as Digital UNIX formerly known as DEC OSF/1) systems</p>
  47 <p>
  48 </p>
  49 <hr />
  50 <h1><a name="description">DESCRIPTION</a></h1>
  51 <p>This document describes various features of HP's (formerly Compaq's,
  52 formerly Digital's) Unix operating system (Tru64) that will affect
  53 how Perl version 5 (hereafter just Perl) is configured, compiled
  54 and/or runs.</p>
  55 <p>
  56 </p>
  57 <h2><a name="compiling_perl_5_on_tru64">Compiling Perl 5 on Tru64</a></h2>
  58 <p>The recommended compiler to use in Tru64 is the native C compiler.
  59 The native compiler produces much faster code (the speed difference is
  60 noticeable: several dozen percentages) and also more correct code: if
  61 you are considering using the GNU C compiler you should use at the
  62 very least the release of 2.95.3 since all older gcc releases are
  63 known to produce broken code when compiling Perl.  One manifestation
  64 of this brokenness is the lib/sdbm test dumping core; another is many
  65 of the op/regexp and op/pat, or ext/Storable tests dumping core
  66 (the exact pattern of failures depending on the GCC release and
  67 optimization flags).</p>
  68 <p>gcc 3.2.1 is known to work okay with Perl 5.8.0.  However, when
  69 optimizing the toke.c gcc likes to have a lot of memory, 256 megabytes
  70 seems to be enough.  The default setting of the process data section
  71 in Tru64 should be one gigabyte, but some sites/setups might have
  72 lowered that.  The configuration process of Perl checks for too low
  73 process limits, and lowers the optimization for the toke.c if
  74 necessary, and also gives advice on how to raise the process limits.</p>
  75 <p>
  76 </p>
  77 <h2><a name="using_large_files_with_perl_on_tru64">Using Large Files with Perl on Tru64</a></h2>
  78 <p>In Tru64 Perl is automatically able to use large files, that is,
  79 files larger than 2 gigabytes, there is no need to use the Configure
  80 -Duselargefiles option as described in INSTALL (though using the option
  81 is harmless).</p>
  82 <p>
  83 </p>
  84 <h2><a name="threaded_perl_on_tru64">Threaded Perl on Tru64</a></h2>
  85 <p>If you want to use threads, you should primarily use the new Perl
  86 5.8.0 threads model by running Configure with -Duseithreads.</p>
  87 <p>The old Perl 5.005 threads is obsolete, unmaintained, and its use is
  88 discouraged.  If you really want it, run Configure with the
  89 -Dusethreads -Duse5005threads options as described in INSTALL.</p>
  90 <p>Either thread model is going to work only in Tru64 4.0 and newer
  91 releases, older operating releases like 3.2 aren't probably going
  92 to work properly with threads.</p>
  93 <p>In Tru64 V5 (at least V5.1A, V5.1B) you cannot build threaded Perl with gcc
  94 because the system header &lt;pthread.h&gt; explicitly checks for supported
  95 C compilers, gcc (at least 3.2.2) not being one of them.  But the
  96 system C compiler should work just fine.</p>
  97 <p>
  98 </p>
  99 <h2><a name="long_doubles_on_tru64">Long Doubles on Tru64</a></h2>
 100 <p>You cannot Configure Perl to use long doubles unless you have at least
 101 Tru64 V5.0, the long double support simply wasn't functional enough
 102 before that.  Perl's Configure will override attempts to use the long
 103 doubles (you can notice this by Configure finding out that the <code>modfl()</code>
 104 function does not work as it should).</p>
 105 <p>At the time of this writing (June 2002), there is a known bug in the
 106 Tru64 libc printing of long doubles when not using ``e'' notation.
 107 The values are correct and usable, but you only get a limited number
 108 of digits displayed unless you force the issue by using <code>printf
 109 &quot;%.33e&quot;,$num</code> or the like.  For Tru64 versions V5.0A through V5.1A, a
 110 patch is expected sometime after perl 5.8.0 is released.  If your libc
 111 has not yet been patched, you'll get a warning from Configure when
 112 selecting long doubles.</p>
 113 <p>
 114 </p>
 115 <h2><a name="db_file_tests_failing_on_tru64">DB_File tests failing on Tru64</a></h2>
 116 <p>The DB_File tests (db-btree.t, db-hash.t, db-recno.t) may fail you
 117 have installed a newer version of Berkeley DB into the system and the
 118 -I and -L compiler and linker flags introduce version conflicts with
 119 the DB 1.85 headers and libraries that came with the Tru64.  For example,
 120 mixing a DB v2 library with the DB v1 headers is a bad idea.  Watch
 121 out for Configure options -Dlocincpth and -Dloclibpth, and check your
 122 /usr/local/include and /usr/local/lib since they are included by default.</p>
 123 <p>The second option is to explicitly instruct Configure to detect the
 124 newer Berkeley DB installation, by supplying the right directories with
 125 <code>-Dlocincpth=/some/include</code> and <code>-Dloclibpth=/some/lib</code> <strong>and</strong> before
 126 running ``make test'' setting your LD_LIBRARY_PATH to <em>/some/lib</em>.</p>
 127 <p>The third option is to work around the problem by disabling the
 128 DB_File completely when build Perl by specifying -Ui_db to Configure,
 129 and then using the BerkeleyDB module from CPAN instead of DB_File.
 130 The BerkeleyDB works with Berkeley DB versions 2.* or greater.</p>
 131 <p>The Berkeley DB 4.1.25 has been tested with Tru64 V5.1A and found
 132 to work.  The latest Berkeley DB can be found from <em><a href="http://www.sleepycat.com">http://www.sleepycat.com</a></em>.</p>
 133 <p>
 134 </p>
 135 <h2><a name="64bit_perl_on_tru64">64-bit Perl on Tru64</a></h2>
 136 <p>In Tru64 Perl's integers are automatically 64-bit wide, there is
 137 no need to use the Configure -Duse64bitint option as described
 138 in INSTALL.  Similarly, there is no need for -Duse64bitall
 139 since pointers are automatically 64-bit wide.</p>
 140 <p>
 141 </p>
 142 <h2><a name="warnings_about_floatingpoint_overflow_when_compiling_perl_on_tru64">Warnings about floating-point overflow when compiling Perl on Tru64</a></h2>
 143 <p>When compiling Perl in Tru64 you may (depending on the compiler
 144 release) see two warnings like this</p>
 145 <pre>
 146     cc: Warning: numeric.c, line 104: In this statement, floating-point overflow occurs in evaluating the expression &quot;1.8e308&quot;. (floatoverfl)
 147         return HUGE_VAL;
 148     -----------^</pre>
 149 <p>and when compiling the POSIX extension</p>
 150 <pre>
 151     cc: Warning: const-c.inc, line 2007: In this statement, floating-point overflow occurs in evaluating the expression &quot;1.8e308&quot;. (floatoverfl)
 152                 return HUGE_VAL;
 153     -------------------^</pre>
 154 <p>The exact line numbers may vary between Perl releases.  The warnings
 155 are benign and can be ignored: in later C compiler releases the warnings
 156 should be gone.</p>
 157 <p>When the file <em>pp_sys.c</em> is being compiled you may (depending on the
 158 operating system release) see an additional compiler flag being used:
 159 <code>-DNO_EFF_ONLY_OK</code>.  This is normal and refers to a feature that is
 160 relevant only if you use the <code>filetest</code> pragma.  In older releases of
 161 the operating system the feature was broken and the NO_EFF_ONLY_OK
 162 instructs Perl not to use the feature.</p>
 163 <p>
 164 </p>
 165 <hr />
 166 <h1><a name="testing_perl_on_tru64">Testing Perl on Tru64</a></h1>
 167 <p>During ``make test'' the <code>comp/cpp</code> will be skipped because on Tru64 it
 168 cannot be tested before Perl has been installed.  The test refers to
 169 the use of the <code>-P</code> option of Perl.</p>
 170 <p>
 171 </p>
 172 <hr />
 173 <h1><a name="ext_odbm_file_odbm_test_failing_with_static_builds">ext/ODBM_File/odbm Test Failing With Static Builds</a></h1>
 174 <p>The ext/ODBM_File/odbm is known to fail with static builds
 175 (Configure -Uusedl) due to a known bug in Tru64's static libdbm
 176 library.  The good news is that you very probably don't need to ever
 177 use the ODBM_File extension since more advanced NDBM_File works fine,
 178 not to mention the even more advanced DB_File.</p>
 179 <p>
 180 </p>
 181 <hr />
 182 <h1><a name="perl_fails_because_of_unresolved_symbol_sockatmark">Perl Fails Because Of Unresolved Symbol sockatmark</a></h1>
 183 <p>If you get an error like</p>
 184 <pre>
 185     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.</pre>
 186 <p>you need to either recompile your Perl in Tru64 4.0D or upgrade your
 187 Tru64 4.0D to at least 4.0F: the <code>sockatmark()</code> system call was
 188 added in Tru64 4.0F, and the IO extension refers that symbol.</p>
 189 <p>
 190 </p>
 191 <hr />
 192 <h1><a name="author">AUTHOR</a></h1>
 193 <p>Jarkko Hietaniemi &lt;<a href="mailto:jhi@iki.fi">jhi@iki.fi</a>&gt;</p>
 194 <table border="0" width="100%" cellspacing="0" cellpadding="3">
 195 <tr><td class="block" style="background-color: #cccccc" valign="middle">
 196 <big><strong><span class="block">&nbsp;README.tru64 - Perl version 5 on Tru64 systems</span></strong></big>
 197 </td></tr>
 198 </table>
 199
 200 </body>
 201
 202 </html>