GNOME Bugzilla – Bug 723083
Unable to re-run configure if a module fails on install
Last modified: 2016-09-17 13:58:19 UTC
Changes in other modules may cause the install phase to fail since the configure phase has not been run to pick up the changes, but since it's not listed in the error phases for install it cannot be choosen in the interactive prompt and ./configure has to be invoked manually from the shell. This patch adds the configure phase to the list of error phases for the install phase, so that it can be inreactively choosen at the jhbuild prompt for failing modules or, if the 'trycheckout' configuration option is enabled, configure can be run to try to automatically recover from a failing module.
Created attachment 267283 [details] [review] autotools: Add configure to the error phases for the install phase Changes in other modules may cause the install phase to fail since the configure phase has not been run to pick up the changes. Add the configure phase to the list of error phases for the install phase, so that it can be inreactively choosen at the jhbuild prompt for failing modules or, if the 'trycheckout' configuration option is enabled, configure can be run to try to automatically recover from a failing module.
The following fix has been pushed: 1c26da7 autotools: Add configure to the error phases for the install phase
Created attachment 335761 [details] [review] autotools: Add configure to the error phases for the install phase Changes in other modules may cause the install phase to fail since the configure phase has not been run to pick up the changes. Add the configure phase to the list of error phases for the install phase, so that it can be inreactively choosen at the jhbuild prompt for failing modules or, if the 'trycheckout' configuration option is enabled, configure can be run to try to automatically recover from a failing module.