[issue32461] the first build after a change to Makefile.pre.in uses the old Makefile

Change by Xavier de Gaye : -- resolution: -> not a bug stage: needs patch -> resolved status: open -> closed ___ Python tracker ___

[issue32461] the first build after a change to Makefile.pre.in uses the old Makefile

Xavier de Gaye added the comment: Two problems: * It is not clear whether one should re-run make after the Makefile file has been updated since the (stale when not using GNU make) Makefile is run to completion. * The 'Makefile' target is remade twice when Makefile.pre.in

[issue32461] the first build after a change to Makefile.pre.in uses the old Makefile

Xavier de Gaye added the comment: Hum, GNU make does re-execute the updated Makefile [1] after the 'Makefile' target has been remade. The problem occurs though with the other make variants that do not have this feature. [1] This may be shown by updating Makefile.pre.in and

[issue32461] the first build after a change to Makefile.pre.in uses the old Makefile

New submission from Xavier de Gaye : After applying the attached Makefile.pre.in.diff that changes the text of the message printed by the 'Makefile' target, the make command gives: $ make CONFIG_FILES=Makefile.pre CONFIG_HEADERS= /bin/sh config.status config.status: creating