Bug 1495 - [x32] No tclibc-glibc.inc found for x32 build
Summary: [x32] No tclibc-glibc.inc found for x32 build
Status: VERIFIED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium major
Target Milestone: 1.2
Assignee: Nitin Kamble
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-09-18 04:28 UTC by Jiajun Xu
Modified: 2011-09-26 19:58 UTC (History)
6 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 Jiajun Xu 2011-09-18 04:28:58 UTC 
tree/branch: poky/1.1_M4
commit: 6462c158fc482e495c1171ffc7747e2ad650a292

With latest 1.1 M4 branch, when I add meta-x32 layer and would like to build a image with x32 support, bitbake will report error that no tclibc-glibc.inc found.

#######
DEBUG: LOAD /home/jxu49/osel/poky-rc2/meta/conf/distro/include/tcmode-default.inc
DEBUG: CONF /home/jxu49/osel/poky-rc2/meta/conf/distro/include/tcmode-default.inc:65: including conf/distro/include/as-needed.inc
DEBUG: BB /home/jxu49/osel/poky-rc2/meta/conf/distro/include/as-needed.inc: handle(data, include)
DEBUG: LOAD /home/jxu49/osel/poky-rc2/meta/conf/distro/include/as-needed.inc
DEBUG: CONF /home/jxu49/osel/poky-rc2/meta/conf/distro/defaultsetup.conf:10: including conf/distro/include/tclibc-glibc.inc
DEBUG: BB conf/distro/include/tclibc-glibc.inc: handle(data, include)
ERROR: Unable to parse conf/bitbake.conf: Could not include required file conf/distro/include/tclibc-glibc.inc
#######
Comment 1 Nitin Kamble 2011-09-19 08:58:51 UTC 
Jiajun,
  Looks like meta-x32 layer is not getting configured properly. How did you configure the meta-x32 layer?

Thanks,
Nitin
Comment 2 Nitin Kamble 2011-09-19 09:49:15 UTC 
There were few commits not pushed to the poky meta-x32 repository. I have pushed those commits, and not it will not give that error.

Thanks,
Nitin
Comment 3 Jiajun Xu 2011-09-26 19:58:24 UTC 
verify the bug as fixed with edison branch.