Log: For newer FreeBSDs the return type of malloc() and free()
is being guessed wrong because the 5.005 configure doesn't
check that if the malloc.h exists that it doesn't simply do
"#error ..." as it does in a number of more recent OS -
I've copied in the test from the blead Configure and
jiggled a few things around and all is hunk-dory - with
this everything compiles and tests fine on
FreeBSD 6.2-RELEASE-p4 (Thanks to Jonathan Stowe)

Log: Tests in t/lib/db-recno.t fail on both of these machines.
The attached patch fixes this by making sure the file DB_File
is being tied to is created. The cause is probably in the
DB_File.xs DoTie_ but I didn't track down where
(patch by Avar)

Here is a rather trivial patch that updates one of the files
in the "vos" subdir.

I keep an old copy of config_h.SH in there so I can see what
changes. (It has a funky name to prevent various clever bits
of Makefile trickery from recognizing it.) This lets me
update my own private copy of config.h easily. This patch
updates my copy of config_h.SH to be the same as the version
in the main directory; no changes are needed to any other
files.

I do not support the native (Configure-based) build method for
this release of perl. However, when perl5.005_03 is built
using the scripts found in the vos subdir, it builds just fine
on current releases of VOS.

Work around bug where Linux libc's have Berekeley DB 2 in them
Patch by Paul Marquess <Paul.Marquess@btinternet.com>,
DB_File's maintainer. His description:

The patch is to work around a problem where some versions of
Linux have a C library with Berkeley DB version 2 embedded in
it. This makes life difficult if you want to build with a
version of Berkeley DB other than the one embedded in
libc. This problem is compounded by the way Perl used to
*always* include the Berkeley DB library when it was being
built. The DB_File patches solves the latter problem, by
retrofitting the fix to Configure et al that was included from
perl 5.6 on. I think your best course of action is to just
apply the 5.00503 patch to the 5.00504 source. I just tried
applying it and it seems ok.