
22 Feb
2017
22 Feb
'17
4:25 p.m.
On Thu, Feb 23, 2017 at 12:25:48AM +1100, Jonathan Gray wrote:
On Mon, Feb 20, 2017 at 07:41:34PM +0100, Paul Kocialkowski wrote:
We now live in a world where python cannot be assumed to be python2. As a matter of fact, it is no longer the default for python on many GNU/Linux distributions.
Running binman with python3 fails, so explicitly request python2 from env in the shebang for running it.
On other systems such as OpenBSD the binary is python2.7 not python2 or python. Though there isn't really a way to handle this with how u-boot builds as I understand it (besides local patches).
I thought, but could be wrong, that "python2" was the canonical way name for the python 2.x binary.
--
Tom