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

[Khem Raj]

On Mon, Oct 4, 2010 at 5:29 PM, Graham Gower <graham.gower at gmail.com> wrote:
> On 5 October 2010 08:53, Graham Gower <graham.gower at gmail.com> wrote:
>> On 4 October 2010 19:43, Jan Paesmans <jan.paesmans at gmail.com> wrote:
>>> 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
>>>
>>> _______________________________________________
>>> Openembedded-devel mailing list
>>> Openembedded-devel at lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>>
>>
>> I've seen this with gcc 4.3.3 also. I've not seen it with 4.4.4 or 4.5.
>>
>> -Graham
>>
>
> Fix here. http://lists.o-hand.com/poky/1917.html
>
> A related bug with the relevant fix has made it in to gcc 4.3.5.
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38591
>
> Is there interest in applying this to the gcc 4.3.3/4.3.4 recipes, or
> would folks be happier with adding gcc 4.3.5? (And can the earlier
> 4.3.x recipes then be removed?)

Just apply this patch to existing 4.3.3 recipes which is deployed by
distros other 4.3.x recipes are not used infact
they can be removed. As far as 4.3.5 is concerned we can backport
fixed into 4.3.3 someday when I have time I will
do it but it needs testing.

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