X-Git-Url: https://perl5.git.perl.org/perl5.git/blobdiff_plain/54c46bd52029aba6a165e4e0063096edcadd1150..4cd32ffe62edd65dfc22629ed249b5a0ec7b6037:/INSTALL diff --git a/INSTALL b/INSTALL index 2401331..84da25e 100644 --- a/INSTALL +++ b/INSTALL @@ -36,13 +36,18 @@ any prefix location by adding "-Dprefix='/some/dir'" to Configure's args. To explicitly name the perl binary, use the command "make install PERLNAME=myperl". +Building perl from source requires an ANSI compliant C-Compiler. +A minimum of C89 is required. Some features available in C99 will +be probed for and used when found. The perl build process does not +rely on anything more than C89. + These options, and many more, are explained in further detail below. If you have problems, corrections, or questions, please see L<"Reporting Problems"> below. For information on what's new in this release, see the -pod/perl5110delta.pod file. For more information about how to find more +pod/perl5133delta.pod file. For more information about how to find more specific detail about changes, see the Changes file. =head1 DESCRIPTION @@ -75,10 +80,10 @@ directory. =head2 Changes and Incompatibilities -Please see pod/perl5110delta.pod for a description of the changes and +Please see pod/perl5133delta.pod for a description of the changes and potential incompatibilities introduced with this release. A few of the most important issues are listed below, but you should refer -to pod/perl5110delta.pod for more detailed information. +to pod/perl5133delta.pod for more detailed information. B This version is not binary compatible with prior releases of Perl. If you have built extensions (i.e. modules that include C code) @@ -93,7 +98,7 @@ The standard extensions supplied with Perl will be handled automatically. On a related issue, old modules may possibly be affected by the changes in the Perl language in the current release. Please see -pod/perl5110delta.pod for a description of what's changed. See your +pod/perl5133delta.pod for a description of what's changed. See your installed copy of the perllocal.pod file for a (possibly incomplete) list of locally installed modules. Also see CPAN::autobundle for one way to make a "bundle" of your currently installed modules. @@ -310,7 +315,7 @@ Natively 64-bit systems need neither -Duse64bitint nor -Duse64bitall. On these systems, it might be the default compilation mode, and there is currently no guarantee that passing no use64bitall option to the Configure process will build a 32bit perl. Implementing -Duse32bit* -options is planned for perl 5.12. +options is planned for a future release of perl. =head3 Long doubles @@ -524,9 +529,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.11.0. +By default, Configure will use the following directories for 5.13.2. $version is the full perl version number, including subversion, e.g. -5.11.0 or 5.9.5, and $archname is a string like sun4-sunos, +5.13.2 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. @@ -787,6 +792,10 @@ can be configured on a per-directory basis, although the default with "-Duserelocatableinc" is that everything is relocated. The initial install is done to the original configured prefix. +This option is not compatible with the building of a shared libperl +("-Duseshrplib"), because in that case perl is linked with an hard-coded +rpath that points at the libperl.so, that cannot be relocated. + =head2 Site-wide Policy settings After Configure runs, it stores a number of common site-wide "policy" @@ -932,7 +941,8 @@ only if it is able to find the gdbm library. To disable certain extensions so that they are not built, use the -Dnoextensions=... and -Donlyextensions=... options. They both accept -a space-separated list of extensions. The extensions listed in +a space-separated list of extensions, such as C. The extensions +listed in C are removed from the list of extensions to build, while the C is rather more severe and builds only the listed extensions. The latter should be used with extreme caution since @@ -1282,7 +1292,7 @@ various other operating systems. If you plan to port Perl to a new architecture, study carefully the section titled "Philosophical Issues in Patching and Porting Perl" -in the file Porting/pumpkin.pod and the file Porting/patching.pod. +in the file Porting/pumpkin.pod and the file pod/perlrepository.pod. Study also how other non-UNIX ports have solved problems. =back @@ -1315,25 +1325,9 @@ process or the Perl build process will not help you with these. =head2 suidperl -suidperl is an optional component, which is normally neither built -nor installed by default. From perlfaq1: - - On some systems, setuid and setgid scripts (scripts written - in the C shell, Bourne shell, or Perl, for example, with the - set user or group ID permissions enabled) are insecure due to - a race condition in the kernel. For those systems, Perl versions - 5 and 4 attempt to work around this vulnerability with an optional - component, a special program named suidperl, also known as sperl. - This program attempts to emulate the set-user-ID and set-group-ID - features of the kernel. - -Because of the buggy history of suidperl, and the difficulty -of properly security auditing as large and complex piece of -software as Perl, we cannot recommend using suidperl and the feature -should be considered deprecated. - -Instead, use a tool specifically designed to handle changes in -privileges, such as B. +suidperl was an optional component of earlier releases of perl. It is no +longer available. Instead, use a tool specifically designed to handle +changes in privileges, such as B. =head1 make depend @@ -1572,6 +1566,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 @@ -1851,7 +1865,7 @@ If make test bombs out, just cd to the t directory and run ./TEST by hand to see if it makes any difference. If individual tests bomb, you can run them by hand, e.g., - cd t ; ./perl -MTestInit op/groups.t + ./perl -MTestInit t/op/groups.t Another way to get more detailed information about failed tests and individual subtests is to cd to the t directory and run @@ -2277,7 +2291,7 @@ http://www.chiark.greenend.org.uk/~sgtatham/bugs.html =head1 Coexistence with earlier versions of perl 5 -Perl 5.11 is not binary compatible with earlier versions of Perl. +Perl 5.12 is not binary compatible with earlier versions of Perl. In other words, you will have to recompile your XS modules. In general, you can usually safely upgrade from one version of Perl (e.g. @@ -2351,9 +2365,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.11.0 + sh Configure -Dprefix=/opt/perl5.13.2 -and adding /opt/perl5.11.0/bin to the shell PATH variable. Such users +and adding /opt/perl5.13.2/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. @@ -2366,13 +2380,13 @@ seriously consider using a separate directory, since development subversions may not have all the compatibility wrinkles ironed out yet. -=head2 Upgrading from 5.10.x or earlier +=head2 Upgrading from 5.11.0 or earlier -B Perl modules having binary parts (meaning that a C compiler is used) will have to be recompiled to be -used with 5.11.0. If you find you do need to rebuild an extension with -5.11.0, you may safely do so without disturbing the older +used with 5.13.2. If you find you do need to rebuild an extension with +5.13.2, you may safely do so without disturbing the older installations. (See L<"Coexistence with earlier versions of perl 5"> above.)