[yocto] Binutils compiling workaround

[Diego Sueiro]

Folks,

I was trying to get binutils (2.10.1 an 2.21) compiled but always getting
this error:

cc1: warnings being treated as errors
/home/dev/yocto-repo/build/tmp/work/armv4t-poky-linux-gnueabi/binutils-2.21-r0/binutils-2.21/gas/config/tc-arm.c:
In function 'parse_operands':
/home/dev/yocto-repo/build/tmp/work/armv4t-poky-linux-gnueabi/binutils-2.21-r0/binutils-2.21/gas/config/tc-arm.c:1895:27:
error: 'firsttype$defined' may be used uninitialized in this function
/home/dev/yocto-repo/build/tmp/work/armv4t-poky-linux-gnueabi/binutils-2.21-r0/binutils-2.21/gas/config/tc-arm.c:1895:27:
error: 'firsttype$index' may be used uninitialized in this function
make[4]: *** [tc-arm.o] Error 1
make[4]: Leaving directory
`/home/dev/yocto-repo/build/tmp/work/armv4t-poky-linux-gnueabi/binutils-2.21-r0/binutils-2.21/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/gas'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/home/dev/yocto-repo/build/tmp/work/armv4t-poky-linux-gnueabi/binutils-2.21-r0/binutils-2.21/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/gas'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/dev/yocto-repo/build/tmp/work/armv4t-poky-linux-gnueabi/binutils-2.21-r0/binutils-2.21/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/gas'
make[1]: *** [all-gas] Error 2
make[1]: Leaving directory
`/home/dev/yocto-repo/build/tmp/work/armv4t-poky-linux-gnueabi/binutils-2.21-r0/binutils-2.21/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi'
make: *** [all] Error 2
FATAL: oe_runmake failed
Function 'do_compile' failed (see
/home/dev/yocto-repo/build/tmp/work/armv4t-poky-linux-gnueabi/binutils-2.21-r0/temp/log.do_compile.26524
for further information)
ERROR: Function 'do_compile' failed (see
/home/dev/yocto-repo/build/tmp/work/armv4t-poky-linux-gnueabi/binutils-2.21-r0/temp/log.do_compile.26524
for further information)


As the compiler was treating warnings as errors I put "--disabe-werror"
on EXTRA_OECONF inside the binutils.inc file.

I don't know if this is the best solution.
What is the root cause of this warning?



Regards,

--
*dS
Diego Sueiro

/*long live rock 'n roll*/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20110202/ce0f9208/attachment.html>