(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.
-
-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.
+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.
=head2 Long Doubles on Tru64
the DB_File extension test db-hash.t may fail by dumping core after
the subtest 21. There really is no good cure as of Tru64 V5.1A expect
installing a newer Berkeley DB and supplying the right directories for
--Dlocincpth=/some/include and -Dloclibpth=/some/lib when running Configure.
+-Dlocincpth=/some/include and -Dloclibpth=/some/lib when running Configure
+B<and> before running "make test" setting your LD_LIBRARY_PATH to /some/lib.
You can also work around the problem by disabling the DB_File by
specifying -Ui_db to Configure, and then using the BerkeleyFile module