[meta-mingw][PATCH] Override SDK_VENDOR
Samuli Piippo
Set SDK_VENDOR to '-w64', which makes the host triplet match what GCC
expect to find when using mingw32-w64. This enables features that are not functional in the classic mingw32, but have been implemented in the mingw32-w64. Disable 32bit libs from the runtime component when compiling for 64bit, which were enabled as a side effect of the GCC config change. Signed-off-by: Samuli Piippo <samuli.piippo@...> --- conf/machine-sdk/include/mingw32-common.inc | 3 +++ .../mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb | 2 ++ 2 files changed, 5 insertions(+) diff --git a/conf/machine-sdk/include/mingw32-common.inc b/conf/machine-sdk/include/mingw32-common.inc index 9011ded..bc6c91e 100644 --- a/conf/machine-sdk/include/mingw32-common.inc +++ b/conf/machine-sdk/include/mingw32-common.inc @@ -1,4 +1,7 @@ SDK_OS = "mingw32" +SDK_VENDOR_mingw32 = "-w64" +SDK_VENDOR_sdkmingw32 = "-w64" + NATIVESDKLIBC = "libc-mingw" PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-for-gcc_mingw32 = "nativesdk-mingw-w64-runtime" diff --git a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb index cf39c6a..9f79ffe 100644 --- a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb +++ b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb @@ -19,6 +19,8 @@ PROVIDES += "virtual/nativesdk-libintl" TOOLCHAIN_OPTIONS = " --sysroot=${STAGING_DIR_TARGET}" +EXTRA_OECONF_x86-64 = "--disable-lib32" + do_configure() { oe_runconf } -- 2.17.1
|
|
[meta-security][zeus][PATCH 1/1] clamav: add INSTALL_CLAMAV_CVD flag to do_install
Charlie Davies
Recipe provides INSTALL_CLAMAV_CVD flag to bypass clamav
cvd db creation. During do_install this flag should be used to conditionally skip install of cvd db if needed. Signed-off-by: Charlie Davies <charles.davies@...> --- recipes-security/clamav/clamav_0.99.4.bb | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/recipes-security/clamav/clamav_0.99.4.bb b/recipes-security/= clamav/clamav_0.99.4.bb index a340b48..1ee3f58 100644 --- a/recipes-security/clamav/clamav_0.99.4.bb +++ b/recipes-security/clamav/clamav_0.99.4.bb @@ -102,7 +102,10 @@ do_install_append_class-target () { install -m 0644 ${WORKDIR}/volatiles.03_clamav ${D}${sysconfdir}/de= fault/volatiles/volatiles.03_clamav sed -i -e 's#${STAGING_DIR_HOST}##g' ${D}${libdir}/pkgconfig/libclam= av.pc rm ${D}/${libdir}/libclamav.so - install -m 666 ${S}/clamav_db/* ${D}/${localstatedir}/lib/clamav/. + if [ "${INSTALL_CLAMAV_CVD}" =3D "1" ]; then + bbnote "CLAMAV installing cvd" + install -m 666 ${S}/clamav_db/* ${D}/${localstatedir}/lib/clamav= /. + fi if ${@bb.utils.contains('DISTRO_FEATURES','systemd','true','false',d= )};then install -D -m 0644 ${WORKDIR}/clamav.service ${D}${systemd_unitd= ir}/system/clamav.service install -d ${D}${sysconfdir}/tmpfiles.d --=20 2.28.0
|
|
[meta-security][zeus][PATCH 0/1] Clamav db creation skip bug
Charlie Davies
Hi Armin,
With the dunfell patch accepted I removed my local fix which has now shown that the same issue exists on the zeus branch (I run my builds against zeus and dunfell). This patch fixes the bug. Cheers, Charlie Charlie Davies (1): clamav: add INSTALL_CLAMAV_CVD flag to do_install recipes-security/clamav/clamav_0.99.4.bb | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) --=20 2.28.0
|
|
[meta-zephyr][PATCH v2] zephyr-kernel: add Zephyr RTOS version 2.3.0 support
yock.gen.mah@...
From: yockgenm <yock.gen.mah@...>
Signed-off-by: yockgenm <yock.gen.mah@...> --- classes/zephyr-kernel-src.bbclass | 12 ++++---- .../qemu/{qemu_4.2.%.bbappend => qemu_%.bbappend} | 0 .../zephyr-kernel/zephyr-kernel-common.inc | 1 + .../zephyr-kernel/zephyr-kernel-src_2.2.bb | 33 ---------------------- .../zephyr-kernel/zephyr-kernel-src_2.3.bb | 24 ++++++++++++++++ .../zephyr-kernel/zephyr-kernel-test.inc | 5 ++-- 6 files changed, 34 insertions(+), 41 deletions(-) rename recipes-devtools/qemu/{qemu_4.2.%.bbappend => qemu_%.bbappend} (100%) delete mode 100644 recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb create mode 100644 recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb diff --git a/classes/zephyr-kernel-src.bbclass b/classes/zephyr-kernel-src.bbclass index 653cb9b..d202293 100644 --- a/classes/zephyr-kernel-src.bbclass +++ b/classes/zephyr-kernel-src.bbclass @@ -1,13 +1,15 @@ #Set relevant variables based on Zephyr kernel version -PREFERRED_VERSION_zephyr-kernel ??= "2.2.0" +PREFERRED_VERSION_zephyr-kernel ??= "2.3.0" -SRCREV = "d39cb42d0920d5658fad358ad5b91de75d747a20" +SRCREV = "b8c78e254ff875680e99c9f131fbe285c4575927" +SRCREV_cmsis = "542b2296e6d515b265e25c6b7208e8fea3014f90" -SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.2-branch \ +SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.3-branch \ + git://github.com/zephyrproject-rtos/cmsis.git;protocol=https;destsuffix=git/modules/cmsis;name=cmsis \ file://0001-cmake-add-yocto-toolchain.patch \ " -PV = "2.2.0" +PV = "2.3.0" LICENSE = "Apache-2.0" LIC_FILES_CHKSUM = "file://LICENSE;md5=fa818a259cbed7ce8bc2a22d35a464fc" @@ -15,7 +17,7 @@ ZEPHYR_TEST_SRCDIR = "tests/legacy/kernel/" python () { src_pn = d.getVar('PREFERRED_VERSION_zephyr-kernel', True) - if src_pn == '2.2.0': + if src_pn == '2.3.0': return else: bb.error("Unsupported Zephyr kernel version requested") diff --git a/recipes-devtools/qemu/qemu_4.2.%.bbappend b/recipes-devtools/qemu/qemu_%.bbappend similarity index 100% rename from recipes-devtools/qemu/qemu_4.2.%.bbappend rename to recipes-devtools/qemu/qemu_%.bbappend diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc index d7147d5..aaf71a8 100644 --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc @@ -14,6 +14,7 @@ ZEPHYR_MAKE_OUTPUT = "zephyr.elf" EXTRA_OECMAKE = " -DZEPHYR_BASE=${S} -DZEPHYR_GCC_VARIANT=yocto -DBOARD=${BOARD} -DARCH=${ARCH} -DCROSS_COMPILE=${CROSS_COMPILE} -DZEPHYR_SYSROOT=${ZEPHYR_SYSROOT} -DZEPHYR_TOOLCHAIN_VARIANT=yocto" +EXTRA_OECMAKE_append_arm = " -DZEPHYR_MODULES=${S}/modules/cmsis" export ZEPHYR_BASE="${S}" diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb deleted file mode 100644 index a3e1c28..0000000 --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb +++ /dev/null @@ -1,33 +0,0 @@ - -LICENSE = "Apache-2.0" -LIC_FILES_CHKSUM = "file://LICENSE;md5=fa818a259cbed7ce8bc2a22d35a464fc" - -# tag v2.2 -SRCREV="d39cb42d0920d5658fad358ad5b91de75d747a20" -SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.2-branch \ - file://0001-cmake-add-yocto-toolchain.patch \ - " -inherit cmake -PV = "2.2.0" -S = "${WORKDIR}/git" - -IMAGE_NO_MANIFEST = "1" -INHIBIT_DEFAULT_DEPS = "1" - -do_configure[noexec] = "1" -do_compile[noexec] = "1" - -do_compile () { -} - -do_install () { - kerneldir=${D}/usr/src/zephyr - install -d $kerneldir - cp -r ${S}/* $kerneldir -} - -PACKAGES = "${PN}" -FILES_${PN} = "/usr/src/zephyr" - -SYSROOT_DIRS += "/usr/src/zephyr" - diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb new file mode 100644 index 0000000..8e8b5b8 --- /dev/null +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb @@ -0,0 +1,24 @@ + +inherit zephyr-kernel-src +inherit cmake + +S = "${WORKDIR}/git" + +IMAGE_NO_MANIFEST = "1" +INHIBIT_DEFAULT_DEPS = "1" + +do_configure[noexec] = "1" +do_compile[noexec] = "1" + + +do_install () { + kerneldir=${D}/usr/src/zephyr + install -d $kerneldir + cp -r ${S}/* $kerneldir +} + +PACKAGES = "${PN}" +FILES_${PN} = "/usr/src/zephyr" + +SYSROOT_DIRS += "/usr/src/zephyr" + diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc index 65da7e8..faf28bd 100644 --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc @@ -1,4 +1,4 @@ -ZEPHYRTESTS_remove = "fifo fp_sharing lifo mbox mem_heap mem_pool \ +ZEPHYRTESTS_remove = "fifo fpu_sharing lifo mbox mem_heap mem_pool \ mem_protect mem_slab msgq mutex pipe profiling sched semaphore \ stack threads tickless timer workq" @@ -23,12 +23,11 @@ ZEPHYRTESTS_remove = "gen_isr_table spinlock smp mp" ZEPHYRTESTS = " \ common \ context \ - critical \ device \ early_sleep \ fatal \ fifo \ - fp_sharing \ + fpu_sharing \ gen_isr_table \ interrupt \ lifo \ -- 2.7.4
|
|
Re: do_unpack() ISO Image
Richard Purdie
On Thu, 2020-09-17 at 20:09 -0700, Chuck Wolber wrote:
You can do the same thing with: do_unpack[depends] += " xorriso:do_populate_sysroot" but note that you want xorriso-native, not xorriso. Cheers, Richard
|
|
Nicolas Jeker
Hi Mike,
On Thu, 2020-09-17 at 22:43 -0700, Mike Thompson via lists.yoctoproject.org wrote: Does anyone know if there is an existing bitbake recipe for buildingI usually search on the OpenEmbedded layer index: http://layers.openembedded.org/layerindex/branch/master/recipes/?q=tailscale Seems like you are right, there seems to be no recipe available. Be aware that not all recipes/layers are listed there, but the majority are. I never used Go in the Yocto/OpenEmbedded environment, but I'm sure somebody else who has more experience will be able to help. To get started with writing a new recipe I usually get my inspiration from similar recipes (similar language, build system, dependencies, etc.). Thanks,
|
|
Mike Thompson <mthompson@...>
Does anyone know if there is an existing bitbake recipe for building the Tailscale client daemon and CLI tool from the following source? A search on Google yielded no obvious links. https://github.com/tailscale/tailscale The Tailscale client for Linux looks to be built using the Go language which is a complete unknown to me. I've built very simple recipes before for basic Makefile and Automake built software, but I suppose Go brings a new set of challenges. If an existing recipe is not available, any words of wisdom before I get started on this? Thanks,
|
|
[meta-zephyr][PATCH] zephyr-kernel: add Zephyr RTOS version 2.3.0 support
yock.gen.mah@...
From: yockgenm <yock.gen.mah@...>
Signed-off-by: yockgenm <yock.gen.mah@...> --- classes/zephyr-kernel-src.bbclass | 12 ++++---- .../{qemu_4.2.%.bbappend => qemu_5.1.%.bbappend} | 0 .../zephyr-kernel/zephyr-kernel-common.inc | 1 + .../zephyr-kernel/zephyr-kernel-src_2.2.bb | 33 ---------------------- .../zephyr-kernel/zephyr-kernel-src_2.3.bb | 24 ++++++++++++++++ .../zephyr-kernel/zephyr-kernel-test.inc | 7 ++--- 6 files changed, 35 insertions(+), 42 deletions(-) rename recipes-devtools/qemu/{qemu_4.2.%.bbappend => qemu_5.1.%.bbappend} (100%) delete mode 100644 recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb create mode 100644 recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb diff --git a/classes/zephyr-kernel-src.bbclass b/classes/zephyr-kernel-src.bbclass index 653cb9b..d202293 100644 --- a/classes/zephyr-kernel-src.bbclass +++ b/classes/zephyr-kernel-src.bbclass @@ -1,13 +1,15 @@ #Set relevant variables based on Zephyr kernel version -PREFERRED_VERSION_zephyr-kernel ??= "2.2.0" +PREFERRED_VERSION_zephyr-kernel ??= "2.3.0" -SRCREV = "d39cb42d0920d5658fad358ad5b91de75d747a20" +SRCREV = "b8c78e254ff875680e99c9f131fbe285c4575927" +SRCREV_cmsis = "542b2296e6d515b265e25c6b7208e8fea3014f90" -SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.2-branch \ +SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.3-branch \ + git://github.com/zephyrproject-rtos/cmsis.git;protocol=https;destsuffix=git/modules/cmsis;name=cmsis \ file://0001-cmake-add-yocto-toolchain.patch \ " -PV = "2.2.0" +PV = "2.3.0" LICENSE = "Apache-2.0" LIC_FILES_CHKSUM = "file://LICENSE;md5=fa818a259cbed7ce8bc2a22d35a464fc" @@ -15,7 +17,7 @@ ZEPHYR_TEST_SRCDIR = "tests/legacy/kernel/" python () { src_pn = d.getVar('PREFERRED_VERSION_zephyr-kernel', True) - if src_pn == '2.2.0': + if src_pn == '2.3.0': return else: bb.error("Unsupported Zephyr kernel version requested") diff --git a/recipes-devtools/qemu/qemu_4.2.%.bbappend b/recipes-devtools/qemu/qemu_5.1.%.bbappend similarity index 100% rename from recipes-devtools/qemu/qemu_4.2.%.bbappend rename to recipes-devtools/qemu/qemu_5.1.%.bbappend diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc index d7147d5..aaf71a8 100644 --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc @@ -14,6 +14,7 @@ ZEPHYR_MAKE_OUTPUT = "zephyr.elf" EXTRA_OECMAKE = " -DZEPHYR_BASE=${S} -DZEPHYR_GCC_VARIANT=yocto -DBOARD=${BOARD} -DARCH=${ARCH} -DCROSS_COMPILE=${CROSS_COMPILE} -DZEPHYR_SYSROOT=${ZEPHYR_SYSROOT} -DZEPHYR_TOOLCHAIN_VARIANT=yocto" +EXTRA_OECMAKE_append_arm = " -DZEPHYR_MODULES=${S}/modules/cmsis" export ZEPHYR_BASE="${S}" diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb deleted file mode 100644 index a3e1c28..0000000 --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb +++ /dev/null @@ -1,33 +0,0 @@ - -LICENSE = "Apache-2.0" -LIC_FILES_CHKSUM = "file://LICENSE;md5=fa818a259cbed7ce8bc2a22d35a464fc" - -# tag v2.2 -SRCREV="d39cb42d0920d5658fad358ad5b91de75d747a20" -SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.2-branch \ - file://0001-cmake-add-yocto-toolchain.patch \ - " -inherit cmake -PV = "2.2.0" -S = "${WORKDIR}/git" - -IMAGE_NO_MANIFEST = "1" -INHIBIT_DEFAULT_DEPS = "1" - -do_configure[noexec] = "1" -do_compile[noexec] = "1" - -do_compile () { -} - -do_install () { - kerneldir=${D}/usr/src/zephyr - install -d $kerneldir - cp -r ${S}/* $kerneldir -} - -PACKAGES = "${PN}" -FILES_${PN} = "/usr/src/zephyr" - -SYSROOT_DIRS += "/usr/src/zephyr" - diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb new file mode 100644 index 0000000..8e8b5b8 --- /dev/null +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb @@ -0,0 +1,24 @@ + +inherit zephyr-kernel-src +inherit cmake + +S = "${WORKDIR}/git" + +IMAGE_NO_MANIFEST = "1" +INHIBIT_DEFAULT_DEPS = "1" + +do_configure[noexec] = "1" +do_compile[noexec] = "1" + + +do_install () { + kerneldir=${D}/usr/src/zephyr + install -d $kerneldir + cp -r ${S}/* $kerneldir +} + +PACKAGES = "${PN}" +FILES_${PN} = "/usr/src/zephyr" + +SYSROOT_DIRS += "/usr/src/zephyr" + diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc index 65da7e8..7ab9bd4 100644 --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc @@ -1,4 +1,4 @@ -ZEPHYRTESTS_remove = "fifo fp_sharing lifo mbox mem_heap mem_pool \ +ZEPHYRTESTS_remove = "fifo fpu_sharing lifo mbox mem_heap mem_pool \ mem_protect mem_slab msgq mutex pipe profiling sched semaphore \ stack threads tickless timer workq" @@ -22,13 +22,12 @@ ZEPHYRTESTS_remove = "gen_isr_table spinlock smp mp" # List of all available kernel tests ZEPHYRTESTS = " \ common \ - context \ - critical \ + context \ device \ early_sleep \ fatal \ fifo \ - fp_sharing \ + fpu_sharing \ gen_isr_table \ interrupt \ lifo \ -- 2.7.4
|
|
Re: QA notification for completed autobuilder build (yocto-3.2_M3.rc1)
Sangeeta Jain
Hi all,
toggle quoted messageShow quoted text
Intel and WR YP QA is planning for QA execution for YP build yocto-3.2_M3.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. Coffee Lake 3. NUC 7 4. NUC 6 5. Edgerouter 6. Beaglebone ETA for completion is next Wednesday, September 23. Thanks, Sangeeta
-----Original Message-----
|
|
do_unpack() ISO Image
Hi all, I have a need to unpack an ISO image during do_unpack. This does not appear to be one of the extensions that is handled by default, so I am working out a way to use xorriso to do this for me. I can get this to work in the following way, but it involves calling an executable running on the build host, which only works by luck since the host executable is the same architecture as what I am currently building. I would like to do this in a portable way that does not break when I try to build for a different architecture. DEPENDS += "xorriso" do_unpack_append() { bb.build.exec_func('unpack_iso', d) } unpack_iso() { /usr/bin/xorriso -osirrox on -indev ${WORKDIR}/${PN}_${PV}.iso -extract / ${S} } From looking at base.bbclass, it _seems_ as if my solution involves something like this: d.appendVarFlag('do_unpack', 'depends', ' xorriso:do_populate_sysroot') But it is unclear exactly where that would go within my recipe. Any thoughts? Thank you, ..Ch:W.. "Perfection must be reached by degrees; she requires the slow hand of time." - Voltaire
|
|
On Thu, Sep 17, 2020 at 6:43 AM Amrun Nisha.R <amrunnishar@...> wrote:
closed you can get is qemuarm64, you can also use package management in image and install/update/remove individual packages. something like https://imxdev.gitlab.io/tutorial/How_to_apt-get_to_the_Yocto_Project_image/
|
|
QA notification for completed autobuilder build (yocto-3.2_M3.rc1)
Pokybuild User
A build flagged for QA (yocto-3.2_M3.rc1) was completed on the autobuilder and is available at:
https://autobuilder.yocto.io/pub/releases/yocto-3.2_M3.rc1 Build hash information: bitbake: 29081375659e3dcf1c578cd98ab2c8a2e9f07ca8 meta-arm: 1f3cf5812c91cdc15f63737bf9b30cce665b2999 meta-gplv2: a8da8eb127a56561bf633ab53bec57fb5dbba537 meta-intel: f7580d72763653893c06e1d9ece7a77c4adb8485 meta-kernel: cb7f0dc5bb1ea0998c8d4fcb486148d4cab575f4 meta-mingw: 30a051401c0a73dfff486ca4d0303b434816200f oecore: 4e7506882cabf3936f0269c2a98f61c7d595d613 poky: c6bc20857cd1bdfd25dfc50e413be84d1d12b189 This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.purdie@...
|
|
Re: [yocto-builds] relocate_sdk.py is failing when installing yocto3.1.2 SDK
Hi Vijay,
I have redirected this thread to the
main yocto list.
The yocto-builds list is for automated
build outputs
rather than discussions.
What distro are you using?
What version of python3 is provided by
that distro?
On Ubu-20.04, fyi:
$ grep python3
/.../oe-core.git/scripts/relocate_sdk.py
#!/usr/bin/env python3 $ python3 --version
Python 3.8.2 ../Randy
On 2020-09-17 9:49 a.m., Ansurivijay
Ramana wrote:
-- # Randy MacLeod # Wind River Linux
|
|
Hello!
Actually I'm working on the DART-IMX8M board. I can able to build the image in linux machine and run it on the board. But for every build, i have to run the image on board. I have checked on the qemu but it is not supported for the machine imx8mq-var-dart.Generally speaking, at the point when we get to working with boards we are needing to interact with the outside world so we have to run on the target hardware. Once U-Boot (or equivalent) is up and running then we speed the development process up using TFTP/NFS to boot the Linux kernel and mount the root file system. It saves all the messing around programming on-board flash devices or SD cards whilst the image is in flux. It also means that all the application developers are using the same and the latest configuration rather than having flash devices with old versions potentially causing problems. It might help a little! -Andy.
|
|
Amrun Nisha.R
Hi,
Actually I'm working on the DART-IMX8M board. I can able to build the image in linux machine and run it on the board. But for every build, i have to run the image on board. I have checked on the qemu but it is not supported for the machine imx8mq-var-dart. Is there any emulator can be used for imx8mq-var-dart?
|
|
Re: wvdial
Maciej Pijanowski
On 17.09.2020 13:35, Maciej Pijanowski
wrote:
It's supposed to be file:// not files:// in the URL.
-- Maciej Pijanowski Embedded Systems Engineer GPG: 9963C36AAC3B2B46 https://3mdeb.com | @3mdeb_com
|
|
Re: wvdial
Maciej Pijanowski
On 17.09.2020 13:25, Zoltan Kerenyi
Nagy wrote:
I'm sorry, but you I think you really do need a pair of glasses
;)
-- Maciej Pijanowski Embedded Systems Engineer GPG: 9963C36AAC3B2B46 https://3mdeb.com | @3mdeb_com
|
|
wvdial
Zoltan Kerenyi Nagy
now there is only one issue has left: ERROR: ExpansionError during parsing /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvdial/wvdial_1.61.bb | ETA: 0:00:00 Traceback (most recent call last): bb.data_smart.ExpansionError: Failure expanding variable do_fetch[file-checksums], expression was ${@bb.fetch.get_checksum_file_list(d)} ${@get_lic_checksum_file_list(d)} which triggered exception NoMethodError: Could not find a fetcher which supports the URL: 'files://typo_pon.wvdial.1.patch' This is the bb recipe: HOMEPAGE = "http://www.alumnit.ca/wiki/?WvDial" DESCRIPTION = "WvDial is a program that makes it easy to connect your Linux workstation to the Internet." LICENSE = "LGPLv2" LIC_FILES_CHKSUM = "file://COPYING.LIB;md5=55ca817ccb7d5b5b66355690e9abc605" inherit pkgconfig DEPENDS = "wvstreams" RDEPENDS_${PN} = "ppp" SRC_URI = "http://${BPN}.googlecode.com/files/${BP}.tar.bz2 \ files://typo_pon.wvdial.1.patch \ " SRC_URI[md5sum] = "d81642557d175d8e0818f4721c27dfcf" SRC_URI[sha256sum] = "a2ce46c8c36870a0f2fa92ea64566df7251fb2d8d5aa2f6ef2b08d188287352e" EXTRA_OEMAKE = "" export WVLINK="${LD}" PARALLEL_MAKE = "" BUILD_CPPFLAGS += "-I${STAGING_INCDIR}/wvstreams" do_configure() { sed -i 's/LDFLAGS+=-luniconf/LIBS+=-luniconf/' ${S}/Makefile } do_install() { oe_runmake prefix=${D}/usr PPPDIR=${D}/etc/ppp/peers install } # http://errors.yoctoproject.org/Errors/Details/186959/ EXCLUDE_FROM_WORLD_libc-musl = "1" Ive re-generated the md5 and sha256 hashes, and all the warnings have disapeared. Here is the patch: if I modify teh 3rd line to "Index: wvdial-1.61/files/pon.wvdial.1" - the error is the same Remove warnings found by lintian Last-Update: 2011-01-09 Index: wvdial-1.61/pon.wvdial.1 =================================================================== --- wvdial-1.61.orig/pon.wvdial.1 2011-01-09 21:33:03.000000000 +0300 +++ wvdial-1.61/pon.wvdial.1 2011-01-09 21:33:15.000000000 +0300 @@ -8,13 +8,11 @@ .SH DESCRIPTION .B pon.wvdial .br -.TR .B poff.wvdial .br .RS Replacement scripts for pon and poff. .RE -\." .SH SEE ALSO .BR wvdial (1), .BR pon (1),
|
|
[PATCH yocto-autobuilder-helper] auh: correct the SMTP server in config file
Alexander Kanavin
Michael Halstead has confirmed this.
Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- scripts/auh-config/upgrade-helper.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/auh-config/upgrade-helper.conf b/scripts/auh-config/upgrade-helper.conf index b012600..5284b4a 100644 --- a/scripts/auh-config/upgrade-helper.conf +++ b/scripts/auh-config/upgrade-helper.conf @@ -9,7 +9,7 @@ blacklist=linux-libc-headers linux-yocto alsa-utils-scripts build-appliance-imag # only recipes belonging to maintainers in whitelist will be attempted #maintainers_whitelist=anibal.limon@... # SMTP server -smtp=smtp1.yoctoproject.org:25 +smtp=mail.yoctoproject.org:25 # from whom should the mails arrive from=auh@... # who should get the status mail with statistics, at the end -- 2.28.0
|
|
Re: RFC: Changes to meta-kernel layer
Jack Mitchell
On 17/09/2020 10:40, Bas Mevissen wrote:
On 2020-09-17 10:43, Paul Barker wrote:I wasn't going to be blamed for the bike shedding of this but as we'veHi folks,I would suggest calling it something like meta-kernel.org then. Naming gotten started I'll stick my oar in. My suggestion would be meta-mainline-kernel, meta-linux-kernel or potentially meta-upstream-kernel but I'm not so keen on that. Vanilla is a confusing term for people not in the game and you know at some point there will be a "vanilla-pi" or "vanilla" board where you're going to hit confusion. As an aside I saw no issues with meta-kernel as it's _the_ Linux kernel from _the_ Linux kernel git repositories. Confusion due to doublespeak from downstream kernel vendors should be corrected and not adhered to. I think these are fair, I can't speak for how other people are using the2) The dunfell branch will no longer get new non-LTS kernel recipes. layer but I would imagine as with most embedded boards, they're using the tooling rather than the plain upstream recipes and the real value is in catching problems with -next kernel compilation early and the fixes/features pushed back to kernel.bbclass. I wouldn't be expecting anything more than basic build and boot on qemu5) Document the test coverage for meta-kernel. We don't test perf, to be fair. Again, IMO the value of this is in the toolchain test and tooling. Compilation patches only I would say. Cheers, Jack.
|
|