Hello all,
When building dunfell branch of meta-linaro for qemux86-64 target, the following parse error occurs:
ERROR: ../sources/meta-linaro/meta-linaro/recipes-linaro/images/linaro-image-lng.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'qcow2' - possibly invalid type name or missing support class
It seems that qcow2 should be replaced with wic.qcow2 according to this oe-core commit from 2017:
https://git.openembedded.org/openembedded-core/commit/?h=dunfell&id=929ba56…
Indeed doing so fixes the build for me.
The master branch of meta-linaro also uses 'qcow2' (while being updated to the newer yocto variable override syntax). So I would expect it to fail similarly there.
Should this get fixed in meta-linaro? Are other people building the dunfell branch successfully?
Thanks,
Ralph
Hello!
We've been encountering a problem with recent kernels (post 5.15,
since this commit [0]) which require a Python3 package called dtschema
[1] (Rob Herring is a maintainer). This is easily installed via pip3
[2] and a recipe works fine for OpenEmbedded [3], even in the ancient
Sumo we're using (well, at least everything seems to be in place).
The problem we're seeing is with the PATH set by the recipe, which has
/poky/build/tmp/hosttools/ as the last bit in it. but no reference to
the native Python (recipe-sysroot-native/usr/bin/python3-native/)
built within OE. This version of Python (3.7.3) is from the host, and
does not have the dtschema package in it (even if it's installed,
dtschema fails to run).
I have tried inheriting python3native in the kernel recipe, which
defines PYTHON and other related variables, but it still fails to use
the right python3 binary.
Is there a recommended way to get the python3-native path into the PATH?
Thanks and greetings!
Daniel Díaz
daniel.diaz(a)linaro.org
[0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?…
[1] https://github.com/devicetree-org/dt-schema/
[2] https://pypi.org/project/dtschema/
[3] https://github.com/mrchapp/meta-lkft/blob/d/add-dtschema/recipes-devtools/p…
There is an issue in meta-rust master, affecting cargo-native with no
checksum.
I will look into.
Regards,
Anibal
On Tue, 19 Oct 2021 at 04:07, <ci_notify(a)linaro.org> wrote:
> Hello CI User,
>
> This is notification from ci.linaro.org for project Qualcomm OpenEmbedded
> RPB (master).
>
> The project Qualcomm OpenEmbedded RPB (master) Build # 692 - Still
> Failing.
>
> Please check console output at
> https://ci.linaro.org/job/lt-qcom-openembedded-rpb-master/692/ to view
> the results.
>
> Thanks!!!
> CI Team
There as been a lot time that is failing NXP iMX, anyone is
using/maintaining it?,
Regarda,
Anibal
El vie., 27 de noviembre de 2020 15:54, <ci_notify(a)linaro.org> escribió:
> Hello CI User,
>
> This is notification from ci.linaro.org for project Reference Platform -
> OpenEmbedded (dunfell).
>
> The project Reference Platform - OpenEmbedded (dunfell) Build # 234 -
> Still Failing.
>
> Please check console output at
> https://ci.linaro.org/job/rpb-openembedded-dunfell/234/ to view the
> results.
>
> Thanks!!!
> CI Team
On Sat, 1 Aug 2020 at 19:40, Sumit Garg via lists.yoctoproject.org
<sumit.garg=linaro.org(a)lists.yoctoproject.org> wrote:
>
> On Sat, 1 Aug 2020 at 14:57, Ryan Harkin <ryan.harkin(a)linaro.org> wrote:
> >
> >
> >
> > On Sat, 1 Aug 2020 at 10:09, Ryan Harkin <ryan.harkin(a)linaro.org> wrote:
> >>
> >> Hi Khem,
> >>
> >> On Fri, 31 Jul 2020, 21:58 Khem Raj, <raj.khem(a)gmail.com> wrote:
> >>>
> >>> On Fri, Jul 31, 2020 at 8:35 AM Ryan Harkin <ryan.harkin(a)linaro.org> wrote:
> >>> >
> >>> > Hello,
> >>> >
> >>> > I'm migrating from Warrior to Dunfell and I'm getting a curious build failure in gcc-sanitizers.
> >>> >
> >>> > Here's the full gory detail:
> >>> > https://pastebin.ubuntu.com/p/nh4cDKMvgS/
> >>> >
> >>> > However, the main error is this:
> >>> >
> >>> > | In file included from ../../../../../../../../../work-shared/gcc-arm-8.3-r2019.03/git/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:193:
> >>> > | ../../../../../../../../../work-shared/gcc-arm-8.3-r2019.03/git/libsanitizer/sanitizer_common/sanitizer_internal_defs.h:317:72: error: size of array 'assertion_failed__1152' is negative
> >>> > | typedef char IMPL_PASTE(assertion_failed_##_, line)[2*(int)(pred)-1]
> >>> >
> >>> > I have no idea where to begin with this. I don't even know why gcc-sanitizers is included in the build, what it does, or why I need it. I'm building an image with dev packages and gcc, so I guess that's why.
> >>> >
> >>> > I've hacked meta-arm to patch sanitizer_platform_limits_posix.cc to null out the macros and that builds fine. I'm sure it won't work, should someone want to use it, mind you.
> >>> >
> >>> > Is there something obvious that I should be doing as part of a Warrior -> Dunfell migration to get this to work?
> >>> >
> >>> > note: Warrior used meta-linaro-toolchain and for Dunfell, it's moved to meta-arm-toolchain.
> >>> >
> >>>
> >>> is gcc 8.3 the latest for linaro
> >>
> >>
> >> I assume so. I haven't attempted to change the default.
> >
> >
> > I'm sorry, that's incorrect: local.conf has an over-ride to specify 8.3.
> > I've just removed it and now it's using 9.3. And it's building fine.
> >
It's using GCC 9.3 from OE core. If you wish to use Arm toolchain then
you need to override the default OE core GCC version with Arm
toolchain GCC version:
GCCVERSION = "arm-9.2"
-Sumit
> > Sumit, do you know if there's a reason for using 9.2 in RPB instead of 9.3?
> >
>
> Arm GCC 9.3 toolchain isn't released yet (see here [1]).
>
> [1] https://developer.arm.com/tools-and-software/open-source-software/developer…
>
> -Sumit
>
> >>
> >>>
> >>> > Regards,
> >>> > Ryan.
> >>> >
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#50161): https://lists.yoctoproject.org/g/yocto/message/50161
> Mute This Topic: https://lists.yoctoproject.org/mt/75909560/1777089
> Group Owner: yocto+owner(a)lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [sumit.garg(a)linaro.org]
> -=-=-=-=-=-=-=-=-=-=-=-