Don't automatically regenerate uconfig.h as part of the microperl build.

This avoids limiting microperl to platforms with a Bourne shell. It also
avoids automated build tools modifying distribution files as part of the
default build targets.

Now that we have a regression test to ensure that uconfig.h is up to date,
the version as shipped will be consistent with uconfig.sh. README.micro
already instructs people to run `make -f Makefile.micro regen_uconfig` if
they edit uconfig.sh, so no change needed there.

diff --git a/Makefile.micro b/Makefile.micro
index ec47c9b..4b738f5 100644 (file)
--- a/Makefile.micro
+++ b/Makefile.micro
@@ -46,7 +46,7 @@ Config = '$$Config{$$1}'
 patch_uconfig:
        $(PERL) -MConfig -pi -e "s/^((?:short|int|long(?:dbl|long)?|ptr|double|[iun]v|u?quad|[iu]\d+|fpos|lseek)(?:size|type)|byteorder|d_quad|quadkind|use64.+)=.*/\\1='"$(Config)"'/g" uconfig.shx
 
-regen_uconfig uconfig.h: uconfig.sh
+regen_uconfig: uconfig.sh config_h.SH
        $(ENV) CONFIG_SH=uconfig.sh CONFIG_H=uconfig.h sh ./config_h.SH
 
 # Do not regenerate perly.c and perly.h.