* seabios build failure @ 2012-01-26 14:35 Christoph Egger 2012-01-26 14:51 ` Ian Campbell 0 siblings, 1 reply; 5+ messages in thread From: Christoph Egger @ 2012-01-26 14:35 UTC (permalink / raw) To: xen-devel@lists.xensource.com 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. 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 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: seabios build failure 2012-01-26 14:35 seabios build failure Christoph Egger @ 2012-01-26 14:51 ` Ian Campbell 2012-01-26 15:01 ` Christoph Egger 0 siblings, 1 reply; 5+ messages in thread From: Ian Campbell @ 2012-01-26 14:51 UTC (permalink / raw) To: Christoph Egger; +Cc: xen-devel@lists.xensource.com 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? 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. ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: seabios build failure 2012-01-26 14:51 ` Ian Campbell @ 2012-01-26 15:01 ` Christoph Egger 2012-01-26 15:06 ` Ian Campbell 0 siblings, 1 reply; 5+ messages in thread From: Christoph Egger @ 2012-01-26 15:01 UTC (permalink / raw) To: Ian Campbell; +Cc: xen-devel@lists.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 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: seabios build failure 2012-01-26 15:01 ` Christoph Egger @ 2012-01-26 15:06 ` Ian Campbell 2012-01-27 14:19 ` Christoph Egger 0 siblings, 1 reply; 5+ messages in thread From: Ian Campbell @ 2012-01-26 15:06 UTC (permalink / raw) To: Christoph Egger; +Cc: xen-devel@lists.xensource.com 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. > > > > 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. There is no current "python" referring to the default version? I think this is something you will need to work out with the SeaBIOS upstream. Ian. > > 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. > > > > > > ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: seabios build failure 2012-01-26 15:06 ` Ian Campbell @ 2012-01-27 14:19 ` Christoph Egger 0 siblings, 0 replies; 5+ messages in thread From: Christoph Egger @ 2012-01-27 14:19 UTC (permalink / raw) To: Ian Campbell; +Cc: xen-devel@lists.xensource.com 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. >>> >>> 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. > > There is no current "python" referring to the default version? > > I think this is something you will need to work out with the SeaBIOS > upstream. > > Ian. > >> >> 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. I see. What python version does SeaBIOS require? I have python 2.5 installed. 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 gmake[6]: *** [out/romlayout16.lds] Error 1 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 ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2012-01-27 14:19 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2012-01-26 14:35 seabios build failure Christoph Egger 2012-01-26 14:51 ` Ian Campbell 2012-01-26 15:01 ` Christoph Egger 2012-01-26 15:06 ` Ian Campbell 2012-01-27 14:19 ` Christoph Egger
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).