X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=Porting%2Fpumpkin.pod;h=4dbbaa108dbc668e95dd6b6eb2413f0467188d58;hb=e42df61ffa4b532a113a57b2965d347ce4da44b3;hp=01b563f26762b7d9fba4c20aa3551591ecd37092;hpb=d7f8936a2fe7fc93635b0b501d1f941d30d3399f;p=p5sagit%2Fp5-mst-13.2.git diff --git a/Porting/pumpkin.pod b/Porting/pumpkin.pod index 01b563f..4dbbaa1 100644 --- a/Porting/pumpkin.pod +++ b/Porting/pumpkin.pod @@ -364,17 +364,25 @@ change the appropriate metaconfig units instead, and regenerate Configure. will regenerate Configure and config_h.SH. Much more information on obtaining and running metaconfig is in the F file -that comes with Perl's metaconfig units. Perl's metaconfig units -should be available on CPAN. A set of units that will work with -perl5.005 is in the file F under -http://www.cpan.org/authors/id/ANDYD/ . The mc_units tar file -should be unpacked in your main perl source directory. Note: those -units were for use with 5.005. There may have been changes since then. -Check for later versions or contact perl5-porters@perl.org to obtain a +that comes with Perl's metaconfig units. + +Since metaconfig is hard to change, running correction scripts after +this generation is sometimes needed. Configure gained complexity over +time, and the order in which config_h.SH is generated can cause havoc +when compiling perl. Therefor, you need to run Porting/config_h.pl +after that generation. All that and more is described in the README +files that come with the metaunits. + +Perl's metaconfig units should be available on CPAN. A set of units +that will work with perl5.9.x is in a file with a name similar to +F under http://www.cpan.org/authors/id/H/HM/HMBRAND/ . +The mc_units tar file should be unpacked in your main perl source directory. +Note: those units were for use with 5.9.x. There may have been changes since +then. Check for later versions or contact perl5-porters@perl.org to obtain a pointer to the current version. -Alternatively, do consider if the F<*ish.h> files might be a better -place for your changes. +Alternatively, do consider if the F<*ish.h> files or the hint files might be +a better place for your changes. =head2 MANIFEST @@ -549,7 +557,7 @@ Let's not force people to keep changing it. =head2 PPPort -F needs to be synchronized to include all +F needs to be synchronized to include all new macros added to .h files (normally perl.h and XSUB.h, but others as well). Since chances are that when a new macro is added the committer will forget to update F, it's the best to diff for @@ -576,6 +584,17 @@ detailed descriptions ought to be easily available somewhere. If you update the subversion number in F, you may need to change the version number near the top of the F file. +=head2 Bumping perl's version + +If you bump perl's version, you will need to update a few things: +the L manpage for the date of release, the version number and +perldelta reference in the top level F (and maybe the copyright +year too), the F file (generated via F, be +sure to run it with the current bleadperl), and the meta-info about +dual-lived modules in Module::Corelist (F does that). +Make sure the numbered feature bundles in F are also +correct. + =head2 Todo The F file contains a roughly-categorized unordered @@ -711,6 +730,8 @@ branches. =head2 Other tests +=over 4 + =item gcc -ansi -pedantic Configure -Dgccansipedantic [ -Dcc=gcc ] will enable (via the cflags script, @@ -795,38 +816,6 @@ they must be fixed eventually.) =over 4 -=item #elif - -The '#elif' preprocessor directive is not understood on all systems. -Specifically, I know that Pyramids don't understand it. Thus instead of the -simple - - #if defined(I_FOO) - # include - #elif defined(I_BAR) - # include - #else - # include - #endif - -You have to do the more Byzantine - - #if defined(I_FOO) - # include - #else - # if defined(I_BAR) - # include - # else - # include - # endif - #endif - -Incidentally, whitespace between the leading '#' and the preprocessor -command is not guaranteed, but is very portable and you may use it freely. -I think it makes things a bit more readable, especially once things get -rather deeply nested. I also think that things should almost never get -too deeply nested, so it ought to be a moot point :-) - =item Probably Prefer POSIX It's often the case that you'll need to choose whether to do @@ -1577,4 +1566,5 @@ All opinions expressed herein are those of the authorZ<>(s). =head1 LAST MODIFIED +27-04-2007 H.Merijn Brand $Id: pumpkin.pod,v 1.23 2000/01/13 19:45:13 doughera Released $