A) The reason to propose this patch following paragraph from README: -------------------- 2) To set sys.platform to something sensible, pass the following environment variable to the configure script: MACHDEP=unicosmk -------------------- The sentence above is not true in all cases. It don't state how to pass as example 1) MACHDEP=abcd export MACHDEP ./configure .... 2) MACHDEP=abcd ./configure .... 3) ./configure MACHDEP=abcd .... The Makefile.pre.in contain dependency rule "Run the configure script": that create config.status if file "configure" is changed as run the script. From above three samples for environment varaible passing only 3) will save MACHDEP into variable CONFIG_ARGS from generated Makefile. The case 2) alwais lost it if config.status is created from makefile rule. The case 1) will work only if developer don't remeber to set it every day. B) The test case (note that MACHDEP isn't valid name!): $ MACHDEP=linuxTEST ./configure --disable-ipv6 checking MACHDEP... linuxTEST .... checking for build directories... done configure: creating ./config.status .... creating Makefile Now lets see if "configure" script is changed: $ touch configure; make /bin/sh ./configure '--disable-ipv6' checking MACHDEP... linux2 <-- MACHDEP is lost .... checking for build directories... done configure: creating ./config.status config.status: creating Makefile.pre config.status: creating Modules/Setup.config config.status: creating pyconfig.h config.status: pyconfig.h is unchanged creating Modules/Setup creating Modules/Setup.local creating Makefile CONFIG_FILES=Makefile.pre CONFIG_HEADERS= /bin/sh config.status config.status: creating Makefile.pre make -f Makefile.pre Makefile make[1]: Entering directory `..../python-release25-maint' make[1]: `Makefile' is up to date. <--- extra make[1]: Leaving directory `..../python-release25-maint' /bin/sh ./Modules/makesetup -c ./Modules/config.c.in \ .... The Makefile was updated, you may need to re-run make. gcc -pthread -c .... .... Note an extra attempt to create Makefile. C) Next lets see after patch: (the python configuration is the same as above): $ touch configure; make /bin/sh ./config.status --recheck running CONFIG_SHELL=/bin/sh /bin/sh ./configure --disable-ipv6 MACHDEP=linuxTEST --no-create --no-recursion checking MACHDEP... linuxTEST <-- MACHDEP is same as at configure time .... checking for build directories... done configure: creating ./config.status creating Modules/Setup creating Modules/Setup.local creating Makefile /bin/sh ./config.status Makefile.pre config.status: creating Makefile.pre /bin/sh ./Modules/makesetup -c ./Modules/config.c.in \ -s Modules \ Modules/Setup.config \ Modules/Setup.local \ Modules/Setup The Makefile was updated, you may need to re-run make. gcc -pthread -c - .... (ignore failure here since MACHDEP=linuxTEST is used only to show problem) D) Rerefence (from autoconf textinfo sections): 4.8.5 Automatic Remaking 7.2 Setting Output Variables (see macro AC_ARG_VAR) 16 config.status Invocation
the change to the configure script looks ok. however you could change the README too. It looks like the changes to the Makefile.pre.in are already applied.
Matthias Klose wrote: > > Matthias Klose added the comment: > > the change to the configure script looks ok. however you could change the README too. This is 5 years old issue. README is not more in repository. As result python lack documentation related to build process. > It looks like the changes to the Makefile.pre.in are already applied. No . But you could ignore this part of issue. Roumen
