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

Jan Paesmans jan.paesmans at gmail.com
Mon Oct 4 11:35:57 UTC 2010


On Mon, Oct 4, 2010 at 11:49 AM, Frans Meulenbroeks
<fransmeulenbroeks at gmail.com> wrote:
> 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 ?

Then it works. I'll try checking the dependencies for glibc-initial.

Jan
>
> Frans
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>




More information about the Openembedded-devel mailing list