(the exact pattern of failures depending on the GCC release and
optimization flags).
+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.
+
=head2 Using Large Files with Perl on Tru64
In Tru64 Perl is automatically able to use large files, that is,
=head2 Threaded Perl on Tru64
-If you want to use threads, you should primarily use the new Perl
+If you want to use threads, you should primarily use the 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 INSTALL.
+Perl threading 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.
-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.
=head2 Long Doubles on Tru64
has not yet been patched, you'll get a warning from Configure when
selecting long doubles.
+=head2 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 DB into the system and the
+-I and -L compiler and linker flags introduce version conflicts with
+the DB 1.85 headers and libraries that came with the Tru64. For example,
+mixing a DB v2 library with the DB 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 DB installation, by supplying the right directories with
+C<-Dlocincpth=/some/include> and C<-Dloclibpth=/some/lib> B<and> before
+running "make test" setting your LD_LIBRARY_PATH to F</some/lib>.
+
+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 CPAN instead of DB_File.
+The BerkeleyDB works with Berkeley DB versions 2.* or greater.
+
+The Berkeley DB 4.1.25 has been tested with Tru64 V5.1A and found
+to work. The latest Berkeley DB can be found from F<http://www.sleepycat.com>.
+
=head2 64-bit Perl on Tru64
In Tru64 Perl's integers are automatically 64-bit wide, there is
https://perl5.git.perl.org / perl5.git / blobdiff