Bug 2050 - [meta-x32] unparsing error happens when build x32 linux image
Summary: [meta-x32] unparsing error happens when build x32 linux image
Status: VERIFIED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.2
Hardware: x86 x86_64
: Medium normal
Target Milestone: 1.2 M4
Assignee: Nitin Kamble
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-03-02 06:07 UTC by yilong, sun
Modified: 2012-04-05 15:54 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description yilong, sun 2012-03-02 06:07:13 UTC 
When i build x32 linux image, parsing error happens，it seems variable  "YOCTO_KERNEL_META_DATA"is not set.

 Detailed error log asfollows： 
 Pseudo is not present but is required, building this first before the main build
ERROR: ParseError at /home/build-sunyl/work-dir/poky/meta-x32/linux/linux-korg_3.1.bb:6: unparsed line: 'YOCTO_KERNEL_META_DATA='                                                          | ETA:  --:--:--
ERROR: Command execution failed: Exited with 1
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

 
Detailed setting information:
Tree/Branch: Poky/1.2_M3
Commit: 320558f494c618f53e0c773db3ea0109476e8359
 
Tree/Branch: meta-x32/master
Commit: 889b052cadc3707012ef1f2f4b7808b82f36dfc2
 
How to build an x32 linux image, please refer to "http://git.yoctoproject.org/cgit/cgit.cgi/experimental/meta-x32/tree/READM E.TXT"
Comment 1 Nitin Kamble 2012-03-06 19:11:06 UTC 
THis is a known issue in the yocto kernel infrastructure for linux-korg recipe.
Bruce have a patch for this, but it is not in the yocto master yet. If you need I can provide the patch, But a real solution is Bruce's patch need to be in yocto master to avoid this issue.

Thanks,
Comment 2 Nitin Kamble 2012-03-19 21:51:25 UTC 
As Bruce's fix is in the oecore master branch this is not issue anymore.
Comment 3 Jiajun Xu 2012-04-05 15:54:15 UTC 
Verify the bug as fixed in 1.2 M4 testing with following commit:

tree/branch: poky/1.2_M4
commit: da6233ea034f35eff59306fdad31f318c340c359