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.
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
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). 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.
-Kevin
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
On Wed, Feb 08, 2012 at 11:32:10AM +0100, Christoph Egger wrote:
On 02/08/12 02:18, Kevin O'Connor wrote:
We can change the seabios makefile to call these scripts with an explicit $(PYTHON).
Awesome!
See the attached patch.
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.
Looks like your version of gcc is defining sections with .rodata.__PRETTY_FUNCTION__ - which is odd as that macro isn't used in the code. Does the second attached patch fix it for you?
-Kevin
On 02/09/12 02:28, Kevin O'Connor wrote:
On Wed, Feb 08, 2012 at 11:32:10AM +0100, Christoph Egger wrote:
On 02/08/12 02:18, Kevin O'Connor wrote:
We can change the seabios makefile to call these scripts with an explicit $(PYTHON).
Awesome!
See the attached patch.
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.
Looks like your version of gcc is defining sections with .rodata.__PRETTY_FUNCTION__ - which is odd as that macro isn't used in the code. Does the second attached patch fix it for you?
-Kevin
Both patches work for me and there are no follow-up errors. Thank you.
Christoph
-
Christoph Egger -
Kevin O'Connor