Thanks; with that the build completed successfully!<br><br>Best Regards,<br>Kaushal<br><br><div class="gmail_quote">2010/12/22 Khem Raj <span dir="ltr"><<a href="mailto:raj.khem@gmail.com">raj.khem@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">2010/12/22 Kaushal Kumar <<a href="mailto:k.kaushal@gmail.com">k.kaushal@gmail.com</a>>:<br>
<div class="im">> Thanks Khem; the build did proceed well without any errors for<br>
> linux-libc-headers.<br>
> Later it fails with a QA staging error for <a href="http://proxy-libintl_20080418.bb" target="_blank">proxy-libintl_20080418.bb</a> (log<br>
> appended).<br>
> I searched the error on web, and could find some related fixes in the<br>
> changelog at:<br>
> <a href="http://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg01075.html" target="_blank">http://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg01075.html</a><br>
> Any idea how I could possibly resolve it. Thanks!<br>
><br>
> Best Regards,<br>
> Kaushal<br>
><br>
> Log:<br>
> ERROR: QA Issue with staging: libstdc++.la failed sanity test (workdir) in<br>
> path /home/avr32/oe/build/tmp/sysroots/avr32-angstrom-linux-uclibc/usr/lib<br>
> ERROR: QA Issue with staging: libsupc++.la failed sanity test (workdir) in<br>
> path /home/avr32/oe/build/tmp/sysroots/avr32-angstrom-linux-uclibc/usr/lib<br>
> FATAL: QA staging was broken by the package built above<br>
> ERROR: Error in executing python function in:<br>
> /home/avr32/oe/openembedded/recipes/proxy-libintl/<a href="http://proxy-libintl_20080418.bb" target="_blank">proxy-libintl_20080418.bb</a><br>
> ERROR: Exception:<type 'exceptions.SystemExit'> Message:1<br>
> ERROR: QA Issue with staging: libstdc++.la failed sanity test (workdir) in<br>
> path /home/avr32/oe/build/tmp/sysroots/avr32-angstrom-linux-uclibc/usr/lib<br>
> ERROR: QA Issue with staging: libsupc++.la failed sanity test (workdir) in<br>
> path /home/avr32/oe/build/tmp/sysroots/avr32-angstrom-linux-uclibc/usr/lib<br>
> FATAL: QA staging was broken by the package built above<br>
<br>
</div>This error is in building gcc-cross and reported a bit later. I would<br>
suggest that you use angstrom-2008<br>
and not angstrom 2010. for avr it uses gcc 4.2.2 which we did not fix<br>
for libtool 2.4 which is used in angstrom 2010<br>
<div><div></div><div class="h5"><br>
<br>
> ERROR: Error in executing python function in:<br>
> /home/avr32/oe/openembedded/recipes/bluez/<a href="http://bluez-dtl1-workaround_1.0.bb" target="_blank">bluez-dtl1-workaround_1.0.bb</a><br>
> ERROR: Exception:<type 'exceptions.SystemExit'> Message:1<br>
> ERROR: Printing the environment of the function<br>
> ERROR: Printing the environment of the function<br>
> ERROR: Function do_qa_staging failed<br>
> ERROR: Function do_qa_staging failed<br>
> ERROR: TaskFailed event exception, aborting<br>
> ERROR: TaskFailed event exception, aborting<br>
> ERROR: Build of<br>
> /home/avr32/oe/openembedded/recipes/bluez/<a href="http://bluez-dtl1-workaround_1.0.bb" target="_blank">bluez-dtl1-workaround_1.0.bb</a><br>
> do_qa_staging failed<br>
> ERROR: Build of<br>
> /home/avr32/oe/openembedded/recipes/proxy-libintl/<a href="http://proxy-libintl_20080418.bb" target="_blank">proxy-libintl_20080418.bb</a><br>
> do_qa_staging failed<br>
><br>
><br>
> 2010/12/22 Bjørn Forsman <<a href="mailto:bjorn.forsman@gmail.com">bjorn.forsman@gmail.com</a>><br>
>><br>
>> Hi,<br>
>><br>
>> 2010/12/21 Khem Raj <<a href="mailto:raj.khem@gmail.com">raj.khem@gmail.com</a>>:<br>
>> > 2010/12/21 Bjørn Forsman <<a href="mailto:bjorn.forsman@gmail.com">bjorn.forsman@gmail.com</a>>:<br>
>> >> Hi,<br>
>> >><br>
>> >> On 21 December 2010 18:44, Khem Raj <<a href="mailto:raj.khem@gmail.com">raj.khem@gmail.com</a>> wrote:<br>
>> >>> On (21/12/10 16:49), Kaushal Kumar wrote:<br>
>> >>>> Hi all,<br>
>> >>>> I am trying to build for AVR32 following the instructions at:<br>
>> >>>> <a href="http://www.openembedded.org/index.php/Getting_started" target="_blank">http://www.openembedded.org/index.php/Getting_started</a><br>
>><br>
>> [...]<br>
>><br>
>> >>> you should not set TARGET_OS yourself on angstrom. You should set<br>
>> >>> ANGSTROMLIBC = "uclibc"<br>
>> >>> in your local.conf and remove TARGET_OS = "linux-uclibc"<br>
>> >>> this should help this case hopefully<br>
>> >><br>
>> >> Why is it that you have to set ANGSTROMLIBC = "uclibc" in local.conf?<br>
>> >> If this is the only libc that builds for AVR32, couldn't OE/bitbake<br>
>> >> select it<br>
>> >> automatically instead of causing a build failure?<br>
>> ><br>
>> > yes it could. If this will always be the case that avr32 will not<br>
>> > support eglibc/glibc<br>
>><br>
>> Ok. I wish I knew how to fix it, because I think it is an annoying<br>
>> little bug! :-)<br>
>><br>
>> Best regards,<br>
>> Bjørn Forsman<br>
><br>
><br>
</div></div></blockquote></div><br>