[oe] trouble building gcc-cross-initial first time

[Frans Meulenbroeks]

2010/10/4 Jan Paesmans <jan.paesmans at gmail.com>:
> Hello all,
>
> When building an image for one of my devices for the first time,
> bitbake always seems to have a problem with building
> gcc-cross-initial. It has the following error:
>
> | In file included from
> /home/jan/src/prodata_openembedded/build/tmp/armv5te/work/armv5te-angstrom-linux-gnueabi/gcc-cross-initial-4.3.3-r13.1/gcc-4.3.3/gcc/sparseset.c:22:
> | /home/jan/src/prodata_openembedded/build/tmp/armv5te/work/armv5te-angstrom-linux-gnueabi/gcc-cross-initial-4.3.3-r13.1/gcc-4.3.3/gcc/system.h:418:
> error: conflicting types for 'strsignal'
> | /usr/include/string.h:564: note: previous declaration of 'strsignal' was here
>
> However, when I restart the exact same bitbake command, the build
> continues without a problem.
>
> I run massive parallel builds with 8 bitbake threads and make -j 8, so
> I suspect that this has something to do with it. One of the tasks the
> is started before is linux-libc-headers_2.6.31.bb, do_package_stage.
> Could it be that this task hasn't finished yet while the
> gcc-cross-initial needs it?
>
> Regards,
>
> Jan
>

It seems to pick up a header file from the host.
It could also be dependent of glibc-initial or so.
What happens if you build from scratch with 1 thread and -j 1 ?

Frans