Bug 13424 - devupstream doesn't work with mutilib
Summary: devupstream doesn't work with mutilib
Status: NEW
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 0.0.0
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 6.2
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2019-07-02 03:30 UTC by Robert Yang
Modified: 2026-10-01 15:48 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Yang 2019-07-02 03:30:35 UTC
Fixed:
    MACHINE = "qemux86-64"
    require conf/multilib.conf
    MULTILIBS = "multilib:lib32"
    DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
    
    PREFERRED_VERSION_lttng-modules = "2.10.10+git%"
    
    $ bitbake world
    
    NOTE: preferred version 2.10.10+git% of lttng-modules not available (for item lib32-lttng-modules)
    NOTE: versions of lttng-modules available: 2.10.10
    ERROR: Multiple versions of lttng-modules are due to be built (/path/to/lttng-modules_2.10.10.bb virtual:devupstream:target:/path/to/lttng-modules_2.10.10.bb). Only one version of a given PN should be built in any given build. You likely need to set PREFERRED_VERSION_lttng-modules to select the correct version or don't depend on multiple versions.
    
    This is because 2.10.10+git% will be built for non-multilib lttng-modules since
    the PREFERRED_VERSION is set, but this version doesn't provide
    lib32-lttng-modules, so 2.10.10 will be built, then the error happens.
    
    Bitbake can't extend an extended recipe, for example:
    virtual:multilib:lib32:virtual:devupstream:target
    
    Or in a reverse order:
    virtual:devupstream:target:virtual:multilib:lib32
Comment 1 Richard Purdie 2021-08-04 17:20:16 UTC
The fix for https://bugzilla.yoctoproject.org/show_bug.cgi?id=11449 should help with this