X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=README.tru64;h=b1305ba4c86b9d0a73aab4f5f079da7ae33badb2;hb=5145b83ccb40455ee1421b25f5971eb7e2a87afc;hp=449fbce7761a214bfb52cbaeb8ae0fe190830876;hpb=5460b889677b9f352c882dbcd4ad4470b8281664;p=p5sagit%2Fp5-mst-13.2.git diff --git a/README.tru64 b/README.tru64 index 449fbce..b1305ba 100644 --- a/README.tru64 +++ b/README.tru64 @@ -50,6 +50,11 @@ 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. +In Tru64 V5 (at least V5.1A, V5.1B) you cannot build threaded Perl with gcc +because the system header 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 You cannot Configure Perl to use long doubles unless you have at least @@ -67,23 +72,27 @@ 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 selecting long doubles. -=head2 db-hash.t failing on Tru64 +=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 Berkeley DB 1.85 coming with the Tru64 is unfortunately buggy. -In general in Tru64 V4.* it seemed to be more stable, but in V5.* -something broke (even though the DB stayed at release 1.85) and -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 -B before running "make test" setting your LD_LIBRARY_PATH to /some/lib. +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 before +running "make test" setting your LD_LIBRARY_PATH to F. -You can also work around the problem by disabling the DB_File by -specifying -Ui_db to Configure, and then using the BerkeleyFile module -from CPAN instead of DB_File. The BerkeleyFile works with Berkeley DB -versions 2.* or greater. +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.0.14 has been tested with Tru64 V5.1A and found +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. =head2 64-bit Perl on Tru64