X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=INSTALL;h=eb7cc07e47d67918e8ef96f5c530bdcf8b8c7c2e;hb=4207d19c588387e70524000ff324caaf2ca59f41;hp=880d2e0abc98dc01e05c60b9990387b7d7bdb74b;hpb=20d572319ce8b690b7b68fec6b58f8ac07b1d362;p=p5sagit%2Fp5-mst-13.2.git

diff --git a/INSTALL b/INSTALL
index 880d2e0..eb7cc07 100644
--- a/INSTALL
+++ b/INSTALL
@@ -524,9 +524,9 @@ The directories set up by Configure fall into three broad categories.
 
 =item Directories for the perl distribution
 
-By default, Configure will use the following directories for 5.12.0.
+By default, Configure will use the following directories for 5.13.0.
 $version is the full perl version number, including subversion, e.g.
-5.12.0 or 5.9.5, and $archname is a string like sun4-sunos,
+5.13.0 or 5.9.5, and $archname is a string like sun4-sunos,
 determined by Configure.  The full definitions of all Configure
 variables are in the file Porting/Glossary.
 
@@ -1561,6 +1561,26 @@ specific rule.
 SCO prior to 3.2.4 may be missing dbmclose().  An upgrade to 3.2.4
 that includes libdbm.nfs (which includes dbmclose()) may be available.
 
+=item error: too few arguments to function 'dbmclose'
+
+Building ODBM_File on some (Open)SUSE distributions might run into this
+error, as the header file is broken. There are two ways to deal with this
+
+ 1. Disable the use of ODBM_FILE
+
+    Configure ... -Dnoextensions=ODBM_File
+
+ 2. Fix the header file, somewhat like this:
+
+    --- a/usr/include/dbm.h  2010-03-24 08:54:59.000000000 +0100
+    +++ b/usr/include/dbm.h  2010-03-24 08:55:15.000000000 +0100
+    @@ -59,4 +59,4 @@ extern datum  firstkey __P((void));
+
+     extern datum   nextkey __P((datum key));
+
+    -extern int     dbmclose __P((DBM *));
+    +extern int     dbmclose __P((void));
+
 =item Note (probably harmless): No library found for -lsomething
 
 If you see such a message during the building of an extension, but
@@ -2340,9 +2360,9 @@ won't interfere with another version.  (The defaults guarantee this for
 libraries after 5.6.0, but not for executables. TODO?)  One convenient
 way to do this is by using a separate prefix for each version, such as
 
-	sh Configure -Dprefix=/opt/perl5.12.0
+	sh Configure -Dprefix=/opt/perl5.13.0
 
-and adding /opt/perl5.12.0/bin to the shell PATH variable.  Such users
+and adding /opt/perl5.13.0/bin to the shell PATH variable.  Such users
 may also wish to add a symbolic link /usr/local/bin/perl so that
 scripts can still start with #!/usr/local/bin/perl.
 
@@ -2357,11 +2377,11 @@ yet.
 
 =head2 Upgrading from 5.11.0 or earlier
 
-B<Perl 5.12.0 is binary incompatible with Perl 5.11.1 and any earlier
+B<Perl 5.13.0 is binary incompatible with Perl 5.11.1 and any earlier
 Perl release.>  Perl modules having binary parts
 (meaning that a C compiler is used) will have to be recompiled to be
-used with 5.12.0.  If you find you do need to rebuild an extension with
-5.12.0, you may safely do so without disturbing the older
+used with 5.13.0.  If you find you do need to rebuild an extension with
+5.13.0, you may safely do so without disturbing the older
 installations.  (See L<"Coexistence with earlier versions of perl 5">
 above.)