.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.32
.\" ========================================================================
.de Sh \" Subsection heading
.de Sp \" Vertical space (when we can't use .PP)
.de Vb \" Begin verbatim text
.de Ve \" End verbatim text
.\" Set up some character translations and predefined strings. \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote. | will give a
.\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to
.\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C'
.\" expand to `' in nroff, nothing in troff, for use with C<>.
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
. tm Index:\\$1\t\\n%\t"\\$2"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
. \" fudge factors for nroff and troff
. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
. \" simple accents for nroff and troff
. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
. \" troff and (daisy-wheel) nroff accents
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
.ds ae a\h'-(\w'a'u*4/10)'e
.ds Ae A\h'-(\w'A'u*4/10)'E
. \" corrections for vroff
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
. \" for low resolution devices (crt and lpr)
.if \n(.H>23 .if \n(.V>19 \
.\" ========================================================================
.TH PERLTRU64 1 "2006-01-07" "perl v5.8.8" "Perl Programmers Reference Guide"
README.tru64 \- Perl version 5 on Tru64 (formerly known as Digital UNIX formerly known as DEC OSF/1) systems
This document describes various features of \s-1HP\s0's (formerly Compaq's,
formerly Digital's) Unix operating system (Tru64) that will affect
how Perl version 5 (hereafter just Perl) is configured, compiled
.Sh "Compiling Perl 5 on Tru64"
.IX Subsection "Compiling Perl 5 on Tru64"
The recommended compiler to use in Tru64 is the native C compiler.
The native compiler produces much faster code (the speed difference is
noticeable: several dozen percentages) and also more correct code: if
you are considering using the \s-1GNU\s0 C compiler you should use at the
very least the release of 2.95.3 since all older gcc releases are
known to produce broken code when compiling Perl. One manifestation
of this brokenness is the lib/sdbm test dumping core; another is many
of the op/regexp and op/pat, or ext/Storable tests dumping core
(the exact pattern of failures depending on the \s-1GCC\s0 release and
gcc 3.2.1 is known to work okay with Perl 5.8.0. However, when
optimizing the toke.c gcc likes to have a lot of memory, 256 megabytes
seems to be enough. The default setting of the process data section
in Tru64 should be one gigabyte, but some sites/setups might have
lowered that. The configuration process of Perl checks for too low
process limits, and lowers the optimization for the toke.c if
necessary, and also gives advice on how to raise the process limits.
.Sh "Using Large Files with Perl on Tru64"
.IX Subsection "Using Large Files with Perl on Tru64"
In Tru64 Perl is automatically able to use large files, that is,
files larger than 2 gigabytes, there is no need to use the Configure
\&\-Duselargefiles option as described in \s-1INSTALL\s0 (though using the option
.Sh "Threaded Perl on Tru64"
.IX Subsection "Threaded Perl on Tru64"
If you want to use threads, you should primarily use the new Perl
5.8.0 threads model by running Configure with \-Duseithreads.
The old Perl 5.005 threads is obsolete, unmaintained, and its use is
discouraged. If you really want it, run Configure with the
\&\-Dusethreads \-Duse5005threads options as described in \s-1INSTALL\s0.
Either thread model is going to work only in Tru64 4.0 and newer
releases, older operating releases like 3.2 aren't probably going
to work properly with threads.
In Tru64 V5 (at least V5.1A, V5.1B) you cannot build threaded Perl with gcc
because the system header <pthread.h> explicitly checks for supported
C compilers, gcc (at least 3.2.2) not being one of them. But the
system C compiler should work just fine.
.Sh "Long Doubles on Tru64"
.IX Subsection "Long Doubles on Tru64"
You cannot Configure Perl to use long doubles unless you have at least
Tru64 V5.0, the long double support simply wasn't functional enough
before that. Perl's Configure will override attempts to use the long
doubles (you can notice this by Configure finding out that the \fImodfl()\fR
function does not work as it should).
At the time of this writing (June 2002), there is a known bug in the
Tru64 libc printing of long doubles when not using \*(L"e\*(R" notation.
The values are correct and usable, but you only get a limited number
of digits displayed unless you force the issue by using \f(CW\*(C`printf
"%.33e",$num\*(C'\fR or the like. For Tru64 versions V5.0A through V5.1A, a
patch is expected sometime after perl 5.8.0 is released. If your libc
has not yet been patched, you'll get a warning from Configure when
.Sh "DB_File tests failing on Tru64"
.IX Subsection "DB_File tests failing on Tru64"
The DB_File tests (db\-btree.t, db\-hash.t, db\-recno.t) may fail you
have installed a newer version of Berkeley \s-1DB\s0 into the system and the
\&\-I and \-L compiler and linker flags introduce version conflicts with
the \s-1DB\s0 1.85 headers and libraries that came with the Tru64. For example,
mixing a \s-1DB\s0 v2 library with the \s-1DB\s0 v1 headers is a bad idea. Watch
out for Configure options \-Dlocincpth and \-Dloclibpth, and check your
/usr/local/include and /usr/local/lib since they are included by default.
The second option is to explicitly instruct Configure to detect the
newer Berkeley \s-1DB\s0 installation, by supplying the right directories with
\&\f(CW\*(C`\-Dlocincpth=/some/include\*(C'\fR and \f(CW\*(C`\-Dloclibpth=/some/lib\*(C'\fR \fBand\fR before
running \*(L"make test\*(R" setting your \s-1LD_LIBRARY_PATH\s0 to \fI/some/lib\fR.
The third option is to work around the problem by disabling the
DB_File completely when build Perl by specifying \-Ui_db to Configure,
and then using the BerkeleyDB module from \s-1CPAN\s0 instead of DB_File.
The BerkeleyDB works with Berkeley \s-1DB\s0 versions 2.* or greater.
The Berkeley \s-1DB\s0 4.1.25 has been tested with Tru64 V5.1A and found
to work. The latest Berkeley \s-1DB\s0 can be found from \fIhttp://www.sleepycat.com\fR.
.Sh "64\-bit Perl on Tru64"
.IX Subsection "64-bit Perl on Tru64"
In Tru64 Perl's integers are automatically 64\-bit wide, there is
no need to use the Configure \-Duse64bitint option as described
in \s-1INSTALL\s0. Similarly, there is no need for \-Duse64bitall
since pointers are automatically 64\-bit wide.
.Sh "Warnings about floating-point overflow when compiling Perl on Tru64"
.IX Subsection "Warnings about floating-point overflow when compiling Perl on Tru64"
When compiling Perl in Tru64 you may (depending on the compiler
release) see two warnings like this
\& cc: Warning: numeric.c, line 104: In this statement, floating-point overflow occurs in evaluating the expression "1.8e308". (floatoverfl)
and when compiling the \s-1POSIX\s0 extension
\& cc: Warning: const-c.inc, line 2007: In this statement, floating-point overflow occurs in evaluating the expression "1.8e308". (floatoverfl)
The exact line numbers may vary between Perl releases. The warnings
are benign and can be ignored: in later C compiler releases the warnings
When the file \fIpp_sys.c\fR is being compiled you may (depending on the
operating system release) see an additional compiler flag being used:
\&\f(CW\*(C`\-DNO_EFF_ONLY_OK\*(C'\fR. This is normal and refers to a feature that is
relevant only if you use the \f(CW\*(C`filetest\*(C'\fR pragma. In older releases of
the operating system the feature was broken and the \s-1NO_EFF_ONLY_OK\s0
instructs Perl not to use the feature.
.SH "Testing Perl on Tru64"
.IX Header "Testing Perl on Tru64"
During \*(L"make test\*(R" the \f(CW\*(C`comp/cpp\*(C'\fR will be skipped because on Tru64 it
cannot be tested before Perl has been installed. The test refers to
the use of the \f(CW\*(C`\-P\*(C'\fR option of Perl.
.SH "ext/ODBM_File/odbm Test Failing With Static Builds"
.IX Header "ext/ODBM_File/odbm Test Failing With Static Builds"
The ext/ODBM_File/odbm is known to fail with static builds
(Configure \-Uusedl) due to a known bug in Tru64's static libdbm
library. The good news is that you very probably don't need to ever
use the ODBM_File extension since more advanced NDBM_File works fine,
not to mention the even more advanced DB_File.
.SH "Perl Fails Because Of Unresolved Symbol sockatmark"
.IX Header "Perl Fails Because Of Unresolved Symbol sockatmark"
\& 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.
you need to either recompile your Perl in Tru64 4.0D or upgrade your
Tru64 4.0D to at least 4.0F: the \fIsockatmark()\fR system call was
added in Tru64 4.0F, and the \s-1IO\s0 extension refers that symbol.
Jarkko Hietaniemi <jhi@iki.fi>
projects / OpenSPARC-T2-SAM / blob