[Openembedded-users] avr32 build issue

[Khem Raj]

2010/12/22 Kaushal Kumar <k.kaushal at gmail.com>:
> Thanks Khem; the build did proceed well without any errors for
> linux-libc-headers.
> Later it fails with a QA staging error for proxy-libintl_20080418.bb (log
> appended).
> I searched the error on web, and could find some related fixes in the
> changelog at:
> http://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg01075.html
> Any idea how I could possibly resolve it. Thanks!
>
> Best Regards,
> Kaushal
>
> Log:
> ERROR: QA Issue with staging: libstdc++.la failed sanity test (workdir) in
> path /home/avr32/oe/build/tmp/sysroots/avr32-angstrom-linux-uclibc/usr/lib
> ERROR: QA Issue with staging: libsupc++.la failed sanity test (workdir) in
> path /home/avr32/oe/build/tmp/sysroots/avr32-angstrom-linux-uclibc/usr/lib
> FATAL: QA staging was broken by the package built above
> ERROR: Error in executing python function in:
> /home/avr32/oe/openembedded/recipes/proxy-libintl/proxy-libintl_20080418.bb
> ERROR: Exception:<type 'exceptions.SystemExit'> Message:1
> ERROR: QA Issue with staging: libstdc++.la failed sanity test (workdir) in
> path /home/avr32/oe/build/tmp/sysroots/avr32-angstrom-linux-uclibc/usr/lib
> ERROR: QA Issue with staging: libsupc++.la failed sanity test (workdir) in
> path /home/avr32/oe/build/tmp/sysroots/avr32-angstrom-linux-uclibc/usr/lib
> FATAL: QA staging was broken by the package built above

This error is in building gcc-cross and reported a bit later. I would
suggest that you use angstrom-2008
and not angstrom 2010. for avr it uses gcc 4.2.2 which we did not fix
for libtool 2.4 which is used in angstrom 2010


> ERROR: Error in executing python function in:
> /home/avr32/oe/openembedded/recipes/bluez/bluez-dtl1-workaround_1.0.bb
> ERROR: Exception:<type 'exceptions.SystemExit'> Message:1
> ERROR: Printing the environment of the function
> ERROR: Printing the environment of the function
> ERROR: Function do_qa_staging failed
> ERROR: Function do_qa_staging failed
> ERROR: TaskFailed event exception, aborting
> ERROR: TaskFailed event exception, aborting
> ERROR: Build of
> /home/avr32/oe/openembedded/recipes/bluez/bluez-dtl1-workaround_1.0.bb
> do_qa_staging failed
> ERROR: Build of
> /home/avr32/oe/openembedded/recipes/proxy-libintl/proxy-libintl_20080418.bb
> do_qa_staging failed
>
>
> 2010/12/22 Bjørn Forsman <bjorn.forsman at gmail.com>
>>
>> Hi,
>>
>> 2010/12/21 Khem Raj <raj.khem at gmail.com>:
>> > 2010/12/21 Bjørn Forsman <bjorn.forsman at gmail.com>:
>> >> Hi,
>> >>
>> >> On 21 December 2010 18:44, Khem Raj <raj.khem at gmail.com> wrote:
>> >>> On (21/12/10 16:49), Kaushal Kumar wrote:
>> >>>> Hi all,
>> >>>> I am trying to build for AVR32 following the instructions at:
>> >>>> http://www.openembedded.org/index.php/Getting_started
>>
>> [...]
>>
>> >>> you should not set TARGET_OS yourself on angstrom. You should set
>> >>> ANGSTROMLIBC = "uclibc"
>> >>> in your local.conf and remove TARGET_OS = "linux-uclibc"
>> >>> this should help this case hopefully
>> >>
>> >> Why is it that you have to set ANGSTROMLIBC = "uclibc" in local.conf?
>> >> If this is the only libc that builds for AVR32, couldn't OE/bitbake
>> >> select it
>> >> automatically instead of causing a build failure?
>> >
>> > yes it could. If this will always be the case that avr32 will not
>> > support eglibc/glibc
>>
>> Ok. I wish I knew how to fix it, because I think it is an annoying
>> little bug! :-)
>>
>> Best regards,
>> Bjørn Forsman
>
>