xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	seabios@seabios.org
Subject: Re: [SeaBIOS] seabios build failure in xen tree
Date: Wed, 8 Feb 2012 11:32:10 +0100	[thread overview]
Message-ID: <4F324F2A.9000308@amd.com> (raw)
In-Reply-To: <20120208011808.GA9541@morn.localdomain>

On 02/08/12 02:18, Kevin O'Connor wrote:
> On Tue, Feb 07, 2012 at 02:35:11PM +0100, Christoph Egger wrote:
>>
>> Adding seabios ML.
>>
>> On 01/26/12 16:06, Ian Campbell wrote:
>>> On Thu, 2012-01-26 at 15:01 +0000, Christoph Egger wrote:
>>>> 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.
>
> We can change the seabios makefile to call these scripts with an
> explicit $(PYTHON).

Awesome!

> However, it's odd that there isn't a default python on your system.
>
> [...]
>> What python version does SeaBIOS require?
>> I have python 2.5 installed.
>
> It should work with python 2.5 - there's nothing really special going
> on in the script.
>
>> I manually created a python symlink to that version and then I get
>> this failure:
>>
>> gmake[6]: Entering directory 'tools/firmware/seabios-dir-remote'
>>    Building ld scripts (version "1.6.3.1-20120127_151243")
>> Fixed space: 0xe05b-0x10000  total: 8101  slack: 5 Percent slack: 0.1%
>> 16bit size:           46336
>> 32bit segmented size: 2005
>> 32bit flat size:      14699
>> 32bit flat init size: 53888
>> Traceback (most recent call last):
>>    File "./tools/layoutrom.py", line 579, in<module>
>>      main()
>>    File "./tools/layoutrom.py", line 576, in main
>>      writeLinkerScripts(sections, entrysym, genreloc, out16,
>> out32seg, out32flag)
>>    File "./tools/layoutrom.py", line 257, in writeLinkerScripts
>>      + COMMONTRAILER
>> TypeError: int argument required
>
> That's quite odd.  This looks data related instead of python related.
> Try running a "make clean" and then "make" in just the seabios
> directory.  If you still see an issue, tar up the seabios "out/"
> directory and mail it to me.

It failed the same way.
I sent you the tarball offlist due its size.

Christoph


-- 
---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-02-08 10:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 13:35 seabios build failure in xen tree Christoph Egger
2012-02-08  1:18 ` Kevin O'Connor
2012-02-08 10:32   ` Christoph Egger [this message]
2012-02-09  1:28     ` Kevin O'Connor
2012-02-09 10:25       ` [SeaBIOS] " 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=4F324F2A.9000308@amd.com \
    --to=christoph.egger@amd.com \
    --cc=kevin@koconnor.net \
    --cc=seabios@seabios.org \
    --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).