[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] seabios build failure

On Thu, 2012-01-26 at 14:35 +0000, Christoph Egger wrote:
> gmake[6]: Entering directory tools/firmware/seabios-dir-remote
>    Building ld scripts (version "")
> env: python: No such file or directory
> gmake[6]: *** [out/romlayout16.lds] Error 127
> The python scripts must be invoked with $(PYTHON) as done
> throughout the build system.

SeaBIOS uses:
$ rgrep -i python tools/firmware/seabios-dir
tools/firmware/seabios-dir/tools/transdump.py:#!/usr/bin/env python
tools/firmware/seabios-dir/tools/buildrom.py:#!/usr/bin/env python
tools/firmware/seabios-dir/tools/checkstack.py:#!/usr/bin/env python
tools/firmware/seabios-dir/tools/encodeint.py:#!/usr/bin/env python
tools/firmware/seabios-dir/tools/layoutrom.py:#!/usr/bin/env python
tools/firmware/seabios-dir/tools/checkrom.py:#!/usr/bin/env python
tools/firmware/seabios-dir/tools/readserial.py:#!/usr/bin/env python
tools/firmware/seabios-dir/tools/readserial.py:Or: apt-get install python-serial
tools/firmware/seabios-dir/tools/checksum.py:#!/usr/bin/env python

Does this not work? Should python be on your $PATH?

Since SeaBIOS is third party code we are not so much at liberty to make
the same sorts of policy decisions as we would for our own code.

You could perhaps attempt to work around this by invoking the recursive
make into the seabios directory with PATH=$(dir-only $(PYTHON):$PATH or
whatever the appropriate runes are.

Or you could try posting a patch to SeaBIOS-devel, I don't know what
their thinking on this sort of thing is.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.