[oe] Yocto 1.7 building alsa-lib do_package fails

[Iorga, Cristian]

Hi,

There might be something wrong with the target machine/processor architecture in your setup..

tmp-angstrom_v2014_12-glibc/work/-angstrom-linux-gnueabi/alsa-lib/1.0.28-r0/ looks strange;
A common root cause will trigger the ipk/opkg error.

Please provide the necessary steps to reproduce the issue.

Regards,
Cristian Iorga
Yocto Project
Intel Corporation


-----Original Message-----
From: openembedded-devel-bounces at lists.openembedded.org [mailto:openembedded-devel-bounces at lists.openembedded.org] On Behalf Of Sven Ebenfeld
Sent: Friday, October 31, 2014 12:14 PM
To: openembedded-devel at lists.openembedded.org
Subject: [oe] Yocto 1.7 building alsa-lib do_package fails

Hi,

When I try to build alsa-lib on master branch of oe-core I get the following error:

ERROR: Function failed: opkg-build execution failed
ERROR: Logfile of failure stored in:
/media/bitbakeTmp/angstrom-dizzy/build/tmp-angstrom_v2014_12-glibc/work/-angstrom-linux-gnueabi/alsa-lib/1.0.28-r0/temp/log.do_package_write_ipk.29979
Log data follows:
| DEBUG: Executing python function sstate_task_prefunc
| DEBUG: Python function sstate_task_prefunc finished
| DEBUG: Executing python function do_package_write_ipk
| DEBUG: Executing python function read_subpackage_metadata
| DEBUG: Python function read_subpackage_metadata finished
| DEBUG: Executing python function do_package_ipk
| *** Error: CONTROL/control is missing field Architecture
|
| opkg-build: Please fix the above errors and try again.
| DEBUG: Python function do_package_ipk finished
| DEBUG: Python function do_package_write_ipk finished
| ERROR: Function failed: opkg-build execution failed
ERROR: Task 1625
(/media/bitbakeTmp/angstrom-dizzy/sources/openembedded-core/meta/recipes-multimedia/alsa/alsa-lib_1.0.28.bb,
do_package_write_ipk) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2214 tasks of which 15 didn't need to be rerun and 1 failed.


I'm using Angstrom setup-scripts on branch angstrom-v2014.12-yocto1.7

Can anybody give me an advice where to look for the source of the problem?

Regards,
Sven
--
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel at lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel