xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: seabios build failure
Date: Thu, 26 Jan 2012 16:01:08 +0100	[thread overview]
Message-ID: <4F216AB4.9020908@amd.com> (raw)
In-Reply-To: <1327589481.26983.95.camel@zakaz.uk.xensource.com>

On 01/26/12 15:51, Ian Campbell wrote:
> 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 "1.6.3.1-20120126_152501")
>> 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?

It is. But the python binary on NetBSD's pkgsrc
is called python<version> to allow concurrent installations of different
python versions.
So I can have: python2.5, python2.6, python2.7, python3.1, etc.

Christoph

>
> 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.
>
> Ian.
>
>


-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85689 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

  reply	other threads:[~2012-01-26 15:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 14:35 seabios build failure Christoph Egger
2012-01-26 14:51 ` Ian Campbell
2012-01-26 15:01   ` Christoph Egger [this message]
2012-01-26 15:06     ` Ian Campbell
2012-01-27 14:19       ` Christoph Egger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F216AB4.9020908@amd.com \
    --to=christoph.egger@amd.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).