On Wed, May 31, 2017 at 10:13 AM, Khem Raj <raj.k...@gmail.com> wrote:
>
> On Wed, May 31, 2017 at 12:22 AM Pello Heriz <
> pello.he...@alumni.mondragon.edu> wrote:
>
>> Hi,
>>
>> I'm trying to build xen-guest-image-minimal with master branch of Yocto,
>> but I keep stuck in the next error:
>>
>> bitbake xen-guest-image-minimal
>> NOTE: /opt/yocto_GE/poky/meta-qt5/recipes-qt/qt5/qtbase_git.bb:
>> base_contains is deprecated, please use bb.utils.contains instead.
>> NOTE: /opt/yocto_GE/poky/meta-qt5/recipes-qt/qt5/qtbase_git.bb:
>> base_contains is deprecated, please use bb.utils.contains instead.
>> WARNING: /opt/yocto_GE/poky/meta-petalinux/recipes-external/
>> external-xilinx-toolchain/libgcc-xilinx.bb: LICENSE_libgcov-dev includes
>> licenses (GPL-3.0) that are not listed in LICENSE
>> Parsing recipes: 100% |##########################################| Time:
>> 0:04:34
>> Parsing of 2477 .bb files complete (0 cached, 2477 parsed). 3310 targets,
>> 312 skipped, 0 masked, 0 errors.
>> WARNING: No recipes available for:
>> /opt/yocto_GE/poky/meta-petalinux/recipes-devtools/
>> python/python-smartpm_%.bbappend
>> WARNING: No bb files matched BBFILE_PATTERN_gpe-layer
>> '^/opt/yocto_GE/poky/meta-openembedded/meta-gpe/'
>> NOTE: Resolving any missing task queue dependencies
>> ERROR: Nothing PROVIDES 'rpmresolve-native'. Close matches:
>> meson-native
>> rpm-native
>> perl-native
>> ERROR: Required build target 'xen-guest-image-minimal' has no buildable
>> providers.
>> Missing or unbuildable dependency chain was: ['xen-guest-image-minimal',
>> 'rpmresolve-native']
>>
>
> It's possible that you do not have matching releases of various layers I
> would first check that
>
Yes master is not stable you need to clone rel-v2017.1 tag​
>
>>
>>
>> The bblayers that I have included to the project are the next ones:
>>
>> BBLAYERS ?= " \
>> ${MY_META_DIR}/meta \
>> ${MY_META_DIR}/meta-poky \
>> ${MY_META_DIR}/meta-yocto-bsp \
>> ${MY_META_DIR}/meta-openembedded/meta-perl \
>> ${MY_META_DIR}/meta-openembedded/meta-systemd \
>> ${MY_META_DIR}/meta-openembedded/meta-gpe \
>> ${MY_META_DIR}/meta-openembedded/meta-python \
>> ${MY_META_DIR}/meta-openembedded/meta-efl \
>> ${MY_META_DIR}/meta-openembedded/meta-ruby \
>> ${MY_META_DIR}/meta-openembedded/meta-filesystems \
>> ${MY_META_DIR}/meta-openembedded/meta-gnome \
>> ${MY_META_DIR}/meta-openembedded/meta-multimedia \
>> ${MY_META_DIR}/meta-openembedded/meta-networking \
>> ${MY_META_DIR}/meta-openembedded/meta-webserver \
>> ${MY_META_DIR}/meta-openembedded/meta-xfce \
>> ${MY_META_DIR}/meta-openembedded/meta-initramfs \
>> ${MY_META_DIR}/meta-openembedded/meta-oe \
>> ${MY_META_DIR}/meta-qt5 \
>> ${MY_META_DIR}/meta-selftest \
>> ${MY_META_DIR}/meta-skeleton \
>> ${MY_META_DIR}/meta-xilinx \
>> ${MY_META_DIR}/meta-xilinx-tools \
>> ${MY_META_DIR}/meta-petalinux \
>> ${MY_META_DIR}/meta-virtualization \
>> ${MY_META_DIR}/meta-xzd \
>> "
>>
>> How can I solve this issue?
>>
>> Regards,
>> Pello
>>
>>
>>
>>
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
