OpenEmbedded

openembedded@lists.linaro.org

4 participants
109 discussions

HOW TO RECOVER YOUR MONEY FROM SCAMMERS THROUGH DIGITAL LIGHT SOLUTION (DLS)

by Arthur Louis

A while back, I jumped into a global property deal, saying folks like me could cash in on hot foreign housing scenes. Real estate - sure, everyone knows it prints money, a big-time industry worldwide. It looked solid at first - they showed me online walkthroughs of places I partly owned, got me pumped. Still, there was this weird vibe nagging me, hard to explain, just wouldn’t quit bugging me inside. I ignored it, though, brushed it off, kept going anyway. One thing I’d say now? Listen to that inner voice - every single time. I kept picturing the steady cash coming in, which blurred how clearly I saw things. At first, they paid me consistent returns, making it feel legit. Over time, though, I poured more money into it. Before long, I tried pulling out bigger amounts - but then the payouts just vanished. The reasons they gave shifted every week, and not long after, they began asking for added charges to fix the withdrawal issues. Still, I’d spent every dollar - put everything I owned into it, thinking it’d be okay. When things went south, I panicked, then remembered a name: {DIGITAL LIGHT SOLUTION}. Found them through some random post while scrolling late at night. Honestly? Didn’t believe they’d help, but they jumped on it fast, scanning stuff I didn't even know existed. Right away, knew these folks weren’t messing around. Used hidden clues online, tracked down where the cash got moved, and then fought to pull it all back into my hands. I'm happy the hard work brought results - my full investment was back in just 72 hours thanks to the team handling my issue. I reached {DIGITAL LIGHT SOLUTION} through T e l e g r a m -- d i g i t a l l i g h t s o l u t i o n And E m a i l.d i g i t a l l i g h t s o l u t i o n (@) q u a l i t y s e r v i c e.c o m - W hats App +1.9.5.4.8.5.6.8.0.4.5

1 day, 12 hours

Hire SAFEGUARD RECOVERY, a Bitcoin recovery specialist, to retrieve stolen or lost coins.

by sophia fourest

I invested $320,000 in Tether (USDT) on a fraudulent website after falling for a romantic scam. I felt completely helpless and in need of assistance after realizing I had been duped. I started looking for a hacker online and found SAFEGUARD RECOVERY. I had optimism because of his professionalism and knowledge. I'm happy to report that SAFEGUARD RECOVERY successfully recovered my stolen money after working relentlessly to do so! I am immensely appreciative of their help and heartily urge anyone in a comparable circumstance to use their services. I'm grateful Email: safeguardbitcoin(a)consultant.com WhatsApp: +44 7426 168300 Website: https://safeguardbitcoin.wixsite.com/safeguard-bitcoin--1

2 days, 11 hours

GENUINE HACKER FOR HIRE CONSULT JAYWEB RECOVERY EXPERT

by Vanesa Drew

If you have lost your bitcoins and are feeling hopeless, I highly recommend Jayweb Bitcoin Recovery. I was in a tough situation after I had lost my bitcoin and thought my money was gone forever. I'm delighted that I decided to test Jayweb. They helped me get my bitcoins back. They kept me informed at every turn, and the procedure was straightforward. It is strongly advised that you get in touch with them if you are experiencing a similar issue. WhatsApp… +1 (305) 452-9075 Email....jay.webb.hack(a)mail.com

4 days, 19 hours

[meta-linaro][PATCH 0/3] Enable host-side QEMU device model (virtio-vga-rutabaga) with gfxstream support

by Lei Zhou

Details please refer to [1]. ./qemu-system-x86_64 \ -m 4G \ -machine pc,accel=kvm,memory-backend=mem,usb=off \ -device virtio-scsi-pci,id=scsi0 \ -device virtio-net-pci,netdev=net0 \ -netdev user,id=net0,hostfwd=tcp::8022-:22 \ -object memory-backend-file,id=mem,size=4G,mem-path=/dev/shm,share=on \ -device virtio-vga-rutabaga,gfxstream-vulkan=on,cross-domain=on,wayland-socket-path=${WAYLAND_SOCK},hostmem=8G [1] https://linaro.atlassian.net/wiki/spaces/ORKO/ pages/28985622530/Building+QEMU+with+virtio-gpu+and+rutabaga_gfx Lei Zhou (3): aemu: add AEMU library gfxstream: add gfxstream recipe rutabaga_gfx_ffi: add as a YOCTO recipe meta-linaro/recipes-graphics/aemu/aemu_git.bb | 18 +++++ .../gfxstream/gfxstream_git.bb | 18 +++++ ...-Use-env-variable-to-pass-in-RUTABAG.patch | 41 ++++++++++++ .../rutabaga-gfx-ffi-crates.inc | 54 +++++++++++++++ .../rutabaga-gfx-ffi_0.1.3.bb | 65 +++++++++++++++++++ 5 files changed, 196 insertions(+) create mode 100644 meta-linaro/recipes-graphics/aemu/aemu_git.bb create mode 100644 meta-linaro/recipes-graphics/gfxstream/gfxstream_git.bb create mode 100644 meta-linaro/recipes-graphics/rutabaga_gfx_ffi/files/0001-rutabaga-gfx-ffi-Use-env-variable-to-pass-in-RUTABAG.patch create mode 100644 meta-linaro/recipes-graphics/rutabaga_gfx_ffi/rutabaga-gfx-ffi-crates.inc create mode 100644 meta-linaro/recipes-graphics/rutabaga_gfx_ffi/rutabaga-gfx-ffi_0.1.3.bb -- 2.34.1

1 year, 5 months

[meta-linaro][PATCH] mesa%.bbappend: add bbappend for enabling amdgpu native device

by Lei Zhou

Signed-off-by: Lei Zhou <lei.zhou(a)linaro.org> --- meta-linaro/recipes-graphics/mesa/mesa_%.bbappend | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 meta-linaro/recipes-graphics/mesa/mesa_%.bbappend diff --git a/meta-linaro/recipes-graphics/mesa/mesa_%.bbappend b/meta-linaro/recipes-graphics/mesa/mesa_%.bbappend new file mode 100644 index 0000000..60d90ef --- /dev/null +++ b/meta-linaro/recipes-graphics/mesa/mesa_%.bbappend @@ -0,0 +1,11 @@ + +EXTRA_OEMESON:append = " \ + -Dgallium-nine=false -Dgallium-xa=disabled -Dglx=dri \ + -Dshared-glapi=enabled -Ddri3=enabled -Degl=enabled -Dgbm=enabled \ + -Dglvnd=true -Dgallium-drivers=radeonsi,virgl -Dplatforms=x11,wayland \ + -Dgles1=disabled -Dgles2=enabled -Dvulkan-drivers=virtio,amd \ + -Dlibunwind=disabled \ +" + +PACKAGECONFIG:append:class-target = "vulkan r600 glvnd" +VULKAN_DRIVERS:append = "virtio,amd" -- 2.34.1

1 year, 5 months

meta-linaro: qcow2 image type in linaro-image-lng.bb

by Ralph Siemsen

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

3 years, 1 month

Kernel and host's Python

by Daniel Díaz

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…

4 years, 3 months

Re: [CI-NOTIFY]: Qualcomm OpenEmbedded RPB (master) - Build # 692 - Still Failing!

by Anibal Limon

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

4 years, 4 months

[meta-linaro][PATCH] optee: remove support

by Jon Mason

From: Jon Mason <jon.mason(a)arm.com> Support for OPTEE is being done in the meta-arm layer now. Remove support here in favor of that. Signed-off-by: Jon Mason <jon.mason(a)arm.com> --- meta-optee/COPYING.MIT | 17 ----- meta-optee/conf/layer.conf | 11 --- .../recipes-security/optee/optee-client.bb | 35 ---------- .../optee/optee-client/tee-supplicant.service | 10 --- .../recipes-security/optee/optee-examples.bb | 42 ----------- ...ow-setting-sysroot-for-libgcc-lookup.patch | 13 ---- .../recipes-security/optee/optee-os_git.bb | 69 ------------------- .../recipes-security/optee/optee-test_git.bb | 49 ------------- 8 files changed, 246 deletions(-) delete mode 100644 meta-optee/COPYING.MIT delete mode 100644 meta-optee/conf/layer.conf delete mode 100644 meta-optee/recipes-security/optee/optee-client.bb delete mode 100644 meta-optee/recipes-security/optee/optee-client/tee-supplicant.service delete mode 100644 meta-optee/recipes-security/optee/optee-examples.bb delete mode 100644 meta-optee/recipes-security/optee/optee-os/0001-allow-setting-sysroot-for-libgcc-lookup.patch delete mode 100644 meta-optee/recipes-security/optee/optee-os_git.bb delete mode 100644 meta-optee/recipes-security/optee/optee-test_git.bb diff --git a/meta-optee/COPYING.MIT b/meta-optee/COPYING.MIT deleted file mode 100644 index fb950dc69feb..000000000000 --- a/meta-optee/COPYING.MIT +++ /dev/null @@ -1,17 +0,0 @@ -Permission is hereby granted, free of charge, to any person obtaining a copy -of this software and associated documentation files (the "Software"), to deal -in the Software without restriction, including without limitation the rights -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies of the Software, and to permit persons to whom the Software is -furnished to do so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in -all copies or substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN -THE SOFTWARE. diff --git a/meta-optee/conf/layer.conf b/meta-optee/conf/layer.conf deleted file mode 100644 index 6b58d43fe101..000000000000 --- a/meta-optee/conf/layer.conf +++ /dev/null @@ -1,11 +0,0 @@ -# We might have a conf and classes directory, append to BBPATH -BBPATH .= ":${LAYERDIR}" - -# We have a recipes directory, add to BBFILES -BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend" - -BBFILE_COLLECTIONS += "meta-optee" -BBFILE_PATTERN_meta-optee := "^${LAYERDIR}/" -BBFILE_PRIORITY_meta-optee = "8" - -LAYERSERIES_COMPAT_meta-optee = "honister" diff --git a/meta-optee/recipes-security/optee/optee-client.bb b/meta-optee/recipes-security/optee/optee-client.bb deleted file mode 100644 index 28cd35463cc0..000000000000 --- a/meta-optee/recipes-security/optee/optee-client.bb +++ /dev/null @@ -1,35 +0,0 @@ -SUMMARY = "OPTEE Client" -HOMEPAGE = "https://github.com/OP-TEE/optee_client" - -LICENSE = "BSD" -LIC_FILES_CHKSUM = "file://${S}/LICENSE;md5=69663ab153298557a59c67a60a743e5b" - -PV = "3.7.0+git${SRCPV}" - -inherit python3native systemd - -SRC_URI = "git://github.com/OP-TEE/optee_client.git \ - file://tee-supplicant.service" -S = "${WORKDIR}/git" - -SRCREV = "bc0ec8ce1e4dc5ae23f4737ef659338b7cd408fe" - -SYSTEMD_SERVICE:${PN} = "tee-supplicant.service" - -do_install() { - oe_runmake install - - install -D -p -m0755 ${S}/out/export/usr/sbin/tee-supplicant ${D}${sbindir}/tee-supplicant - - install -D -p -m0644 ${S}/out/export/usr/lib/libteec.so.1.0 ${D}${libdir}/libteec.so.1.0 - ln -sf libteec.so.1.0 ${D}${libdir}/libteec.so - ln -sf libteec.so.1.0 ${D}${libdir}/libteec.so.1 - - cp -a ${S}/out/export/usr/include ${D}/usr/ - - sed -i -e s:/etc:${sysconfdir}:g \ - -e s:/usr/bin:${bindir}:g \ - ${WORKDIR}/tee-supplicant.service - - install -D -p -m0644 ${WORKDIR}/tee-supplicant.service ${D}${systemd_system_unitdir}/tee-supplicant.service -} diff --git a/meta-optee/recipes-security/optee/optee-client/tee-supplicant.service b/meta-optee/recipes-security/optee/optee-client/tee-supplicant.service deleted file mode 100644 index ffb54d3900d2..000000000000 --- a/meta-optee/recipes-security/optee/optee-client/tee-supplicant.service +++ /dev/null @@ -1,10 +0,0 @@ -[Unit] -Description=TEE Supplicant - -[Service] -User=root -EnvironmentFile=-/etc/default/tee-supplicant -ExecStart=/usr/sbin/tee-supplicant $OPTARGS - -[Install] -WantedBy=basic.target diff --git a/meta-optee/recipes-security/optee/optee-examples.bb b/meta-optee/recipes-security/optee/optee-examples.bb deleted file mode 100644 index f590c44470b3..000000000000 --- a/meta-optee/recipes-security/optee/optee-examples.bb +++ /dev/null @@ -1,42 +0,0 @@ -SUMMARY = "OP-TEE examples" -HOMEPAGE = "https://github.com/linaro-swg/optee_examples" - -LICENSE = "GPLv2" -LIC_FILES_CHKSUM = "file://${S}/LICENSE;md5=cd95ab417e23b94f381dafc453d70c30" - -DEPENDS = "optee-client optee-os python3-pycrypto-native" - -inherit python3native - -SRC_URI = "git://github.com/linaro-swg/optee_examples.git" -SRCREV = "559b2141c16bf0f57ccd72f60e4deb84fc2a05b0" - -S = "${WORKDIR}/git" - -OPTEE_CLIENT_EXPORT = "${STAGING_DIR_HOST}${prefix}" -TEEC_EXPORT = "${STAGING_DIR_HOST}${prefix}" -TA_DEV_KIT_DIR = "${STAGING_INCDIR}/optee/export-user_ta" - -EXTRA_OEMAKE = " TA_DEV_KIT_DIR=${TA_DEV_KIT_DIR} \ - OPTEE_CLIENT_EXPORT=${OPTEE_CLIENT_EXPORT} \ - TEEC_EXPORT=${TEEC_EXPORT} \ - HOST_CROSS_COMPILE=${TARGET_PREFIX} \ - TA_CROSS_COMPILE=${TARGET_PREFIX} \ - V=1 \ - " - -do_compile() { - oe_runmake -} - -do_install () { - mkdir -p ${D}${nonarch_base_libdir}/optee_armtz - mkdir -p ${D}${bindir} - install -D -p -m0755 ${S}/out/ca/* ${D}${bindir} - install -D -p -m0444 ${S}/out/ta/* ${D}${nonarch_base_libdir}/optee_armtz -} - -FILES:${PN} += "${nonarch_base_libdir}/optee_armtz/" - -# Imports machine specific configs from staging to build -PACKAGE_ARCH = "${MACHINE_ARCH}" diff --git a/meta-optee/recipes-security/optee/optee-os/0001-allow-setting-sysroot-for-libgcc-lookup.patch b/meta-optee/recipes-security/optee/optee-os/0001-allow-setting-sysroot-for-libgcc-lookup.patch deleted file mode 100644 index 17127d0b0819..000000000000 --- a/meta-optee/recipes-security/optee/optee-os/0001-allow-setting-sysroot-for-libgcc-lookup.patch +++ /dev/null @@ -1,13 +0,0 @@ -diff --git a/mk/gcc.mk b/mk/gcc.mk -index fc38c4d..77b8d74 100644 ---- a/mk/gcc.mk -+++ b/mk/gcc.mk -@@ -12,7 +12,7 @@ nostdinc$(sm) := -nostdinc -isystem $(shell $(CC$(sm)) \ - -print-file-name=include 2> /dev/null) - - # Get location of libgcc from gcc --libgcc$(sm) := $(shell $(CC$(sm)) $(CFLAGS$(arch-bits-$(sm))) $(comp-cflags$(sm)) \ -+libgcc$(sm) := $(shell $(CC$(sm)) $(LIBGCC_LOCATE_CFLAGS) $(CFLAGS$(arch-bits-$(sm))) $(comp-cflags$(sm)) \ - -print-libgcc-file-name 2> /dev/null) - - # Define these to something to discover accidental use diff --git a/meta-optee/recipes-security/optee/optee-os_git.bb b/meta-optee/recipes-security/optee/optee-os_git.bb deleted file mode 100644 index 581233f9ff39..000000000000 --- a/meta-optee/recipes-security/optee/optee-os_git.bb +++ /dev/null @@ -1,69 +0,0 @@ -SUMMARY = "OP-TEE Trusted OS" -DESCRIPTION = "OPTEE OS" - -LICENSE = "BSD" -LIC_FILES_CHKSUM = "file://${S}/LICENSE;md5=c1f21c4f72f372ef38a5a4aee55ec173" - -PV="3.7.0+git${SRCPV}" - -inherit deploy python3native - -DEPENDS = "python3-pycrypto-native python3-pyelftools-native" - -SRCREV = "a2fa5018cb595a9cd9ab62e82c7485ca57a62084" -SRC_URI = "git://github.com/OP-TEE/optee_os.git \ - file://0001-allow-setting-sysroot-for-libgcc-lookup.patch \ - " - -S = "${WORKDIR}/git" - -OPTEEMACHINE ?= "${MACHINE}" -OPTEEOUTPUTMACHINE ?= "${MACHINE}" - -EXTRA_OEMAKE = "PLATFORM=${OPTEEMACHINE} CFG_ARM64_core=y \ - CROSS_COMPILE_core=${HOST_PREFIX} \ - CROSS_COMPILE_ta_arm64=${HOST_PREFIX} \ - NOWERROR=1 \ - ta-targets=ta_arm64 \ - LDFLAGS= \ - LIBGCC_LOCATE_CFLAGS=--sysroot=${STAGING_DIR_HOST} \ - " - -OPTEE_ARCH:armv7a = "arm32" -OPTEE_ARCH:aarch64 = "arm64" - -do_compile() { - unset LDFLAGS - oe_runmake all CFG_TEE_TA_LOG_LEVEL=0 -} - -do_install() { - #install core on boot directory - install -d ${D}${nonarch_base_libdir}/firmware/ - - install -m 644 ${B}/out/arm-plat-${OPTEEOUTPUTMACHINE}/core/*.bin ${D}${nonarch_base_libdir}/firmware/ - #install TA devkit - install -d ${D}/usr/include/optee/export-user_ta/ - - for f in ${B}/out/arm-plat-${OPTEEOUTPUTMACHINE}/export-ta_${OPTEE_ARCH}/* ; do - cp -aR $f ${D}/usr/include/optee/export-user_ta/ - done -} - -PACKAGE_ARCH = "${MACHINE_ARCH}" - -do_deploy() { - install -d ${DEPLOYDIR}/optee - for f in ${D}${nonarch_base_libdir}/firmware/*; do - install -m 644 $f ${DEPLOYDIR}/optee/ - done -} - -addtask deploy before do_build after do_install - -FILES:${PN} = "${nonarch_base_libdir}/firmware/" -FILES:${PN}-dev = "/usr/include/optee" - -INSANE_SKIP:${PN}-dev = "staticdev" - -INHIBIT_PACKAGE_STRIP = "1" diff --git a/meta-optee/recipes-security/optee/optee-test_git.bb b/meta-optee/recipes-security/optee/optee-test_git.bb deleted file mode 100644 index 15d66ee8d145..000000000000 --- a/meta-optee/recipes-security/optee/optee-test_git.bb +++ /dev/null @@ -1,49 +0,0 @@ -SUMMARY = "OP-TEE sanity testsuite" -HOMEPAGE = "https://github.com/OP-TEE/optee_test" - -LICENSE = "BSD & GPLv2" -LIC_FILES_CHKSUM = "file://${S}/LICENSE.md;md5=daa2bcccc666345ab8940aab1315a4fa" - -inherit python3native - -DEPENDS = "optee-client optee-os python3-pycrypto-native" - -PV = "3.7.0+git${SRCPV}" - -SRC_URI = "git://github.com/OP-TEE/optee_test.git \ - " -S = "${WORKDIR}/git" - -SRCREV = "227d6f4c40eaa6f84fe049b9e48c7b27ad7fab08" - -OPTEE_CLIENT_EXPORT = "${STAGING_DIR_HOST}${prefix}" -TEEC_EXPORT = "${STAGING_DIR_HOST}${prefix}" -TA_DEV_KIT_DIR = "${STAGING_INCDIR}/optee/export-user_ta" - -EXTRA_OEMAKE = " TA_DEV_KIT_DIR=${TA_DEV_KIT_DIR} \ - OPTEE_CLIENT_EXPORT=${OPTEE_CLIENT_EXPORT} \ - TEEC_EXPORT=${TEEC_EXPORT} \ - CROSS_COMPILE_HOST=${TARGET_PREFIX} \ - CROSS_COMPILE_TA=${TARGET_PREFIX} \ - V=1 \ - " - -do_compile() { - # Top level makefile doesn't seem to handle parallel make gracefully - oe_runmake xtest - oe_runmake ta -} - -do_install () { - install -D -p -m0755 ${S}/out/xtest/xtest ${D}${bindir}/xtest - - # install path should match the value set in optee-client/tee-supplicant - # default TEEC_LOAD_PATH is /lib - mkdir -p ${D}${nonarch_base_libdir}/optee_armtz/ - install -D -p -m0444 ${S}/out/ta/*/*.ta ${D}${nonarch_base_libdir}/optee_armtz/ -} - -FILES:${PN} += "${nonarch_base_libdir}/optee_armtz/" - -# Imports machine specific configs from staging to build -PACKAGE_ARCH = "${MACHINE_ARCH}" -- 2.20.1

4 years, 4 months

Re: [CI-NOTIFY]: Reference Platform - OpenEmbedded (dunfell) - Build # 234 - Still Failing!

by Anibal Limon

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

5 years, 2 months

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

OpenEmbedded