Totally mystified w/ V2

Eric W. Biederman ebiederman at lnxi.com
Sat Oct 25 15:23:00 CEST 2003


Dave Ashley <linuxbios at xdr.com> writes:

> Found earlier post which suggests doing this:
> buildtarget via/epia
> Guessed that this had to be done within targets directory. Got
> this error:
> ... lots cut, hashed over before
> TypeError: long requires exactly 1 argument; 2 given
> 
> Ended up modifying util/newconfig/config.g>
>     rule term:		NUM			{{ return long(NUM, 10) }}
> 		|	HEX_PREFIX HEX_NUM	{{ return long(HEX_NUM, 16) }}
> 
> 
> becomes
> 
>     rule term:		NUM			{{ return long(NUM) }}
> 		| HEX_PREFIX HEX_NUM {{ return long(eval("0x" + HEX_NUM)) }}
> 
> 
> Hopefully this is compatible with newer versions of python and that
> the long() can take 1 or 2 arguments...

Python is not very compatible.  All of python 2 should be supported.
python 1.x is a problem and 

> Then it dies on this:
> gcc ... -o crt0.o crt0.s
> crt0.s: Assembler messages:
> crt0.s:16821: Error: missing ')'
> crt0.s:16821: Error: junk `L+0x03)' after expression
> crt0.s:16822: Error: missing ')'
> crt0.s:16822: Error: junk `L|0x80)' after expression
> crt0.s:16835: Error: missing ')'
> crt0.s:16835: Error: junk `L+0x00)' after expression
> etc, etc.

Without seeing what generated lines for crt0.s are this looks
bad.  But my hunch is that this is still a tool chain issue.

All I can tell clearly is whatever is being passed to the assmebler
is being parsed properly.  That is either because it is bad in
the first place (likel), or we are accidentally using some extended
assembler feature.

Eric



More information about the coreboot mailing list