Bug 2560 - [multilib]lib64-core-image-sato build failed due to sanity check
Summary: [multilib]lib64-core-image-sato build failed due to sanity check
Status: RESOLVED NOTABUG
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-06-08 08:56 UTC by Hongna Xu
Modified: 2012-06-18 07:03 UTC (History)
6 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hongna Xu 2012-06-08 08:56:44 UTC
tree/branch: poky/master
git info :348da93e283b2b8454fd9cde80d4b17378e2a168

when build lib64-core-image-sato with multilib enable, i got the error:
*****************************************
ERROR:  OE-core's config sanity checker detected a potential misconfiguration.
    Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
    Following is the list of potential problems / advisories:

    Toolchain tunings invalid:
Multilib 'lib64' (x86-64) is also the default tuning.

ERROR: Execution of event handler 'check_sanity_eventhandler' failed
ERROR: Command execution failed: Exited with 1

Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
**************************************************
The configuration I used for build is like following:
#######
MACHINE = "qemux86-64"
require conf/multilib.conf
MULTILIBS = "multilib:lib64"
DEFAULTTUNE_virtclass-multilib-lib64 = "x86-64"
#####
Comment 1 Richard Purdie 2012-06-13 15:46:14 UTC
Getting a warning about this configuration makes sense, you're trying to build two sets of librbaries with exactly the same optimisations. If this is one of our standard test cases, I think we need to adpat it, maybe by selecting a different tuning for one set of multilib libraries...
Comment 2 Jiajun Xu 2012-06-18 07:03:17 UTC
(In reply to comment #1)
> Getting a warning about this configuration makes sense, you're trying to
> build two sets of librbaries with exactly the same optimisations. If this is
> one of our standard test cases, I think we need to adpat it, maybe by
> selecting a different tuning for one set of multilib libraries...

Hi Richard,
It's OK for us to remove such case if it's expected. Meanwhile, we also have a test case to build 32bit library against qemux86, which has not been reported as warning in sanity.bbclass. I think the 2 combinations should be consistent if 64bit library build against qemux86-64 should fail.