| commit | 406ab2f331555cfcf320fe2a77949d7f8af7ab32 | |
| author | Cleber Rosa <crosa@redhat.com> | |
| Mon, 26 Aug 2019 15:58:32 +0000 (26 11:58 -0400) | ||
| committer | Eduardo Habkost <ehabkost@redhat.com> | |
| Tue, 27 Aug 2019 19:57:24 +0000 (27 16:57 -0300) | ||
| tree | 05370dee5173e523b58cb2a0e61015722ef16ea0 | treesnapshot (tar.gz zip) |
| parent | 73a5a775d273d34221889dc91be7580e26a9584d | commitdiff |
configure: more resilient Python version capture
The current approach to capture the Python version is fragile, as it
was demonstrated by a very specific build of Python 3 on Fedora 29
that, under non-interactive shells would print multiline version
information.
The (badly) stripped version output would be sent to config-host.mak,
producing bad syntax and rendering the makefiles unusable. Now, the
Python versions is printed by configure, but only a simple (and better
controlled variable) indicating whether the build system is using
Python 2 is kept on config-host.mak.
Signed-off-by: Cleber Rosa <crosa@redhat.com>
Message-Id: <20190826155832.17427-1-crosa@redhat.com>
Reviewed-by: Tony Nguyen <tony.nguyen@bt.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
The current approach to capture the Python version is fragile, as it
was demonstrated by a very specific build of Python 3 on Fedora 29
that, under non-interactive shells would print multiline version
information.
The (badly) stripped version output would be sent to config-host.mak,
producing bad syntax and rendering the makefiles unusable. Now, the
Python versions is printed by configure, but only a simple (and better
controlled variable) indicating whether the build system is using
Python 2 is kept on config-host.mak.
Signed-off-by: Cleber Rosa <crosa@redhat.com>
Message-Id: <20190826155832.17427-1-crosa@redhat.com>
Reviewed-by: Tony Nguyen <tony.nguyen@bt.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
| configure | diffblobblamehistory | |
| tests/Makefile.include | diffblobblamehistory |