Re: [yocto] Which recipe for qmicli?
Thank you very much Nicolas. On 10/31/19, Nicolas Dechesne wrote: > On Thu, Oct 31, 2019 at 7:26 AM JH wrote: >> >> Hi, >> >> The qmicli is in libqmi-utils in Ubuntu package, but I could not find >> Yocto libqmi-utils, only libqmi recipe, is qmicli in libqmi? > > yes, it is there. There isn't a 1 to 1 mapping between debian and OE > package names. But if you build libqmi recipe, you will see that the > libqmi package includes qmicli. > >> >> Thank you. >> >> Kind regards, >> >> - jh >> -- >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] NooB: applying new patches to older files, where do I find the older files?
On 31-10-2019 01:52, Randy MacLeod wrote: On 10/30/19 8:16 AM, R wrote: Hello List, First I'm working on a unsupported distro (Manjaro) and try to get an older version (2.7.1) of poky working. I have ask a question before and Ross Burton pointed me in the direction of a patch. Now I'm trying to apply that patch, however the patch is for a newer version of the original files, so I need to make my own patch for the older version of these files. (reason: WARNING: Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.) The patch says: the file to be patch is e.g. /linux-user/syscall.c My question is where can I find the original syscall.c before any patches are applied to it? Hi Robert, This file and the patch are for the qemu package. You can run: $ bitbake -c patch qemu-native <--- host build or $ bitbake -c patch qemu <--- target build to get all the patches that are listed in the qemu recipe in poky: meta/recipes-devtools/qemu/qemu_3.1.1.1.bb and meta/recipes-devtools/qemu/qemu.inc applied to unpacked source. The patched source will be in (this is on master branch): /tmp-glibc/work/x86_64-linux/qemu-native/4.1.0-r0/qemu-4.1.0/linux-user/syscall.c poky might just be /tmp/ instead of /tmp-glibc/ In my case the log of the patching is in: tmp-glibc/work/x86_64-linux/qemu-native/4.1.0-r0/temp/log.do_patch Just to be complete: I have tried the latest warrior branch and that worked fine. My objective is not just to get it working be also to get a grip on how the system works :-) Super. Have you looked at: https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html and perhaps: https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#finding-the-temporary-source-code will be useful now. Manipulating patches by hand can be tedious. There's a tool called wiggle: https://linux.die.net/man/1/wiggle which can help but may be too much for you to deal with initially. Actually, I suggest that you build on a supported distro initially to understand the basic workflow and then decide if you want to figure out how to make Arch/Manjaro work. ../Randy Thanks, Robert. Thanks Randy, Very helpful, especially the trigger to look into the development manual. I know starting with a supported distro would be the smarter choice. But then it would just work and I would probably make tiny steps in changes, this way I'm pulled right into the belly of the "beast" and I will learn much faster how it works :-) Disadvantage is that I maybe overwhelmed, so I will ask a question like this one, occasionally. Robert -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto builds and svn offline
Hi,
The problem:
In our project we have some parts located in svn server far. This server due to
"unknown" reasons very often is not accessible. And I noticed that yocto always
tries to access the svn server. Not like the other components in download
directory. Something worse, if it does not access the server, it erases all the
trunks, tags we had already in download/svn directory. I made a simple test
erasing sstate-cache and tmp, and disconnected the cable of my machine.
Everything goes fine till svn recipes. Here is the shortest recipe:
SUMMARY = "Linux0 web pages"
DESCRIPTION = "Set of static web pages to be displayed during update."
LICENSE = "CLOSED"
PV = "117434"
SRC_URI = " \
svn://cocosubversion/svn/Embedded/Valve\&Actuator/DVPII/trunk/Linux0Web;module=trunk;protocol=http;rev=${PV}
\
file://ww-linux0-web-deploy.sh \
"
S = "${WORKDIR}/trunk"
INSTALL_DIR = "/www/ww-linux0-web"
FILES_${PN} += " \
${INSTALL_DIR}/index.html.ww_failed_to_boot \
${INSTALL_DIR}/index.html.ww_failed_to_program \
${INSTALL_DIR}/index.html.ww_update_in_progress \
"
# Skip the unwanted steps
do_configure[noexec] = "1"
do_compile[noexec] = "1"
do_install () {
install -d ${D}${INSTALL_DIR}
install -m 644 ${S}/index.html.ww_failed_to_boot ${D}${INSTALL_DIR}
install -m 644 ${S}/index.html.ww_failed_to_program ${D}${INSTALL_DIR}
install -m 644 ${S}/index.html.ww_update_in_progress ${D}${INSTALL_DIR}
install -d ${D}${bindir}
install -m 755 ${WORKDIR}/ww-linux0-web-deploy.sh ${D}${bindir}
}
How can we solve that issue?
***
The information in this email is confidential and intended solely for the
individual or entity to whom it is addressed. If you have received this email
in error please notify the sender by return e-mail, delete this email, and
refrain from any disclosure or action based on the information.
***
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto builds and svn offline
Update:
I made a simple new recipe
SUMMARY = "Test of svn relationship with yocto"
LICENSE = "CLOSED"
PV = "119889"
SRC_URI =
"svn://cocosubversion/svn/Embedded/Shared/;module=yoctotest;protocol=http;rev=${PV}"
FILES_${PN} = "${WW_PATH}/test.txt"
WW_PATH="/opt/ww"
S = "${WORKDIR}/yoctotest/"
do_install () {
# ${PN}-sys
#
==
install -d ${D}/${WW_PATH}/
install -m 0644 ${S}/test.txt ${D}/${WW_PATH}/
}
It is build offline without problem. (But first time online of course) May we
speak then about an issue with svn fetcher in yocto?
Cordially
Georgi
From: Georgi Georgiev
Sent: Thursday, October 31, 2019 12:59 PM
To: 'yocto@yoctoproject.org'
Subject: Yocto builds and svn offline
Hi,
The problem:
In our project we have some parts located in svn server far. This server due to
"unknown" reasons very often is not accessible. And I noticed that yocto always
tries to access the svn server. Not like the other components in download
directory. Something worse, if it does not access the server, it erases all the
trunks, tags we had already in download/svn directory. I made a simple test
erasing sstate-cache and tmp, and disconnected the cable of my machine.
Everything goes fine till svn recipes. Here is the shortest recipe:
SUMMARY = "Linux0 web pages"
DESCRIPTION = "Set of static web pages to be displayed during update."
LICENSE = "CLOSED"
PV = "117434"
SRC_URI = " \
svn://cocosubversion/svn/Embedded/Valve\&Actuator/DVPII/trunk/Linux0Web;module=trunk;protocol=http;rev=${PV}
\
file://ww-linux0-web-deploy.sh \
"
S = "${WORKDIR}/trunk"
INSTALL_DIR = "/www/ww-linux0-web"
FILES_${PN} += " \
${INSTALL_DIR}/index.html.ww_failed_to_boot \
${INSTALL_DIR}/index.html.ww_failed_to_program \
${INSTALL_DIR}/index.html.ww_update_in_progress \
"
# Skip the unwanted steps
do_configure[noexec] = "1"
do_compile[noexec] = "1"
do_install () {
install -d ${D}${INSTALL_DIR}
install -m 644 ${S}/index.html.ww_failed_to_boot ${D}${INSTALL_DIR}
install -m 644 ${S}/index.html.ww_failed_to_program ${D}${INSTALL_DIR}
install -m 644 ${S}/index.html.ww_update_in_progress ${D}${INSTALL_DIR}
install -d ${D}${bindir}
install -m 755 ${WORKDIR}/ww-linux0-web-deploy.sh ${D}${bindir}
}
How can we solve that issue?
***
The information in this email is confidential and intended solely for the
individual or entity to whom it is addressed. If you have received this email
in error please notify the sender by return e-mail, delete this email, and
refrain from any disclosure or action based on the information.
***
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] GCC version 8 upgrade
How silly would it be to try and get GCC sdk v8 complied and installed for Jethro? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] NooB: applying new patches to older files, where do I find the older files?
On 10/31/19 6:36 AM, R wrote: On 31-10-2019 01:52, Randy MacLeod wrote: On 10/30/19 8:16 AM, R wrote: Hello List, First I'm working on a unsupported distro (Manjaro) and try to get an older version (2.7.1) of poky working. I have ask a question before and Ross Burton pointed me in the direction of a patch. Now I'm trying to apply that patch, however the patch is for a newer version of the original files, so I need to make my own patch for the older version of these files. (reason: WARNING: Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.) The patch says: the file to be patch is e.g. /linux-user/syscall.c My question is where can I find the original syscall.c before any patches are applied to it? Hi Robert, This file and the patch are for the qemu package. You can run: $ bitbake -c patch qemu-native <--- host build or $ bitbake -c patch qemu <--- target build to get all the patches that are listed in the qemu recipe in poky: meta/recipes-devtools/qemu/qemu_3.1.1.1.bb and meta/recipes-devtools/qemu/qemu.inc applied to unpacked source. The patched source will be in (this is on master branch): /tmp-glibc/work/x86_64-linux/qemu-native/4.1.0-r0/qemu-4.1.0/linux-user/syscall.c poky might just be /tmp/ instead of /tmp-glibc/ In my case the log of the patching is in: tmp-glibc/work/x86_64-linux/qemu-native/4.1.0-r0/temp/log.do_patch Just to be complete: I have tried the latest warrior branch and that worked fine. My objective is not just to get it working be also to get a grip on how the system works :-) Super. Have you looked at: https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html and perhaps: https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#finding-the-temporary-source-code will be useful now. Manipulating patches by hand can be tedious. There's a tool called wiggle: https://linux.die.net/man/1/wiggle which can help but may be too much for you to deal with initially. Actually, I suggest that you build on a supported distro initially to understand the basic workflow and then decide if you want to figure out how to make Arch/Manjaro work. ../Randy Thanks, Robert. Thanks Randy, Very helpful, especially the trigger to look into the development manual. I know starting with a supported distro would be the smarter choice. But then it would just work and I would probably make tiny steps in changes, this way I'm pulled right into the belly of the "beast" and I will learn much faster how it works :-) Disadvantage is that I maybe overwhelmed, so I will ask a question like this one, occasionally. Robert Makes sense I suppose, good luck, questioned welcomed. There are also people on freenode IRC #oe if you are interested. A few Yocto devs have used ArchLinux so you're not breaking completely new ground, FYI. ../Randy -- # Randy MacLeod # Wind River Linux -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-announce] [ANNOUNCEMENT] Yocto Project 2.6.4 (thud 20.0.4) Released
Hello, We are pleased to announce the Yocto Project 2.6.4 (thud-20.0.4) Release is now available for download. http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.4/poky-thud-20.0.4.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.6.4/poky-thud-20.0.4.tar.bz2 A gpg signed version of these release notes is available at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.4/RELEASENOTES Full Test Report: http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.4/testreport.txt Thank you for everyone's contributions to this release. Note: Yocto Project has updated the expiration date on the release signing key. Please import https://downloads.yoctoproject.org/releases/yocto/keys/yocto-release-key.asc to verify RELEASENOTES and git tags. Sincerely, Vineela Tummalapalli Yocto Project Build and Release vineela.tummalapa...@intel.com - - yocto-2.6.4 Release Notes - - - --- Repositories/Downloads - --- Repository Name: poky Repository Location: https://git.yoctoproject.org/git/poky Branch: thud Tag: yocto-2.6.4 Git revision: 51f6145f8f99a02df1dad937684f014b0172e72a Release Artefact: poky-thud-20.0.4 md5: 9859b2ac90ced909bdd7293125295348 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.4/poky-thud-20.0.4.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.6.4/poky-thud-20.0.4.tar.bz2 Repository Name: openembedded-core Repository Location: https://git.openembedded.org/openembedded-core Branch: thud Tag: yocto-2.6.4 Git revision: cd7cf933b3235560ec71576d8f3836dff736a39f Release Artefact: oecore-thud-20.0.4 md5: a2f1d7fa021ca3d37c5c3a65ea27b2d7 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.4/oecore-thud-20.0.4.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.6.4/oecore-thud-20.0.4.tar.bz2 Repository Name: meta-mingw Repository Location: https://git.yoctoproject.org/git/meta-mingw Branch: thud Tag: yocto-2.6.4 Git revision: 6556cde16fbdf42c7edae89bb186e5ae4982eff5 Release Artefact: meta-mingw-thud-20.0.4 md5: 8e20b388086db80a1420cfa5be5f5573 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.4/meta-mingw-thud-20.0.4.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.6.4/meta-mingw-thud-20.0.4.tar.bz2 Repository Name: meta-intel Repository Location: https://git.yoctoproject.org/git/meta-intel Branch: thud Tag: yocto-2.6.4 Git revision: c200851435f39acd2fe4abbf7a05fbf617833964 Release Artefact: meta-intel-thud-20.0.4 md5: 4696150e7676a926baf0975e252f0964 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.4/meta-intel-thud-20.0.4.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.6.4/meta-intel-thud-20.0.4.tar.bz2 Repository Name: meta-gplv2 Repository Location: https://git.yoctoproject.org/git/meta-gplv2 Branch: thud Tag: yocto-2.6.4 Git revision: aabc30f3bd03f97326fb8596910b94639fea7575 Release Artefact: meta-gplv2-thud-20.0.4 md5: 478bd5348e9b64fde6df18a82f691fd3 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.4/meta-gplv2-thud-20.0.4.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.6.4/meta-gplv2-thud-20.0.4.tar.bz2 - --- Known Issues - --- Bug 13273 - Systemtap doesn't work on beaglebone https://bugzilla.yoctoproject.org/show_bug.cgi?id=13273 - --- Security Fixes - --- curl: Security fix for CVE-2019-5482 libsolv: Security fix for CVEs: gnutls: Fix CVE-2019-3829 and CVE-2019-3836 glibc: Security fix for cve wget: Security fixes CVE-2018-20483 sqlite3: Security fix for CVE-2019-8457 perl: Fix CVE-2018-18311 to 18314 unzip: fix CVE-2019-13232 elfutils: CVE fix for elfutils qemu: Fix 4 CVEs pango: fix CVE-2019-1010238 patch: fix CVE-2019-13638 libxslt: fix CVE-2019-13117 CVE-2019-13118 libxslt: Cve fix CVE-2019-11068 python3: Fix CVEs python: Fix 3 CVEs binutils: Fix 4 CVEs binutils: Security fix for CVE-2019-12972 binutils: Security fix for CVE-2019-1 gcc: Security fix for CVE-2019-14250 libcomps: fix CVE-2019-3817 glib-2.0: fix CVE-2019-13012 dbus: fix CVE-2019-12749 curl: fix CVE-2018-16890 CVE-2019-3822 CVE-2019-3823 python3: fix CVE-2019-9740 patch: fix CVE-2019-13636 - --- Fixes - --- build-appliance-image: Update to thud head revision Revert "OpkgPM: use --add-ignore-recommends to process BAD_RECOMMENDATIONS" build-appliance-image: Update to thud head revision poky.conf: Bump version for 2.6.4 thud release kernel-devsrc: check for localversion files in the kernel source tree arch-arm64.inc: Lower the priority of aarch64 in MACHINEOVERRIDES kernel.bbclass: fix installation of modules signing certificates bitbake: cookerdata: Add mc conffiles hashes to cache hash uninative: Update to 2.7 release gnupg: Do not apply -Woverride-init guard for gcc >= 9 libgpg-error: Fix build with gawk 5.x qemu: fix build issue on new hosts with glibc 2.30 jso
Re: [yocto] GCC version 8 upgrade
On 31/10/2019 15:49, Bishop . wrote: How silly would it be to try and get GCC sdk v8 complied and installed for Jethro? Quite. GCC upgrades are tricky things to do at the best of times. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] GCC version 8 upgrade
On Thu, Oct 31, 2019 at 11:49:38AM -0400, Bishop . wrote: > How silly would it be to try and get GCC sdk v8 complied and installed for > Jethro? Lets call it "quite demanding" instead of "outright silly", ok? Greetz > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ——— Josef Holzmayr Software Developer Embedded Systems Tel: +49 8444 9204-48 Fax: +49 8444 9204-50 R-S-I Elektrotechnik GmbH & Co. KG Woelkestrasse 11 D-85301 Schweitenkirchen www.rsi-elektrotechnik.de ——— Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393 Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg Ust-IdNr: DE 128592548 _ Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363 Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg USt-IdNr.: DE 128592548 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified
poky linux build fails when ARM erratum mfix linker switch is specified in local.conf: TARGET_LD_ARCH_append += " -mfix-cortex-a53-843419” causes build failure. Please advise how to use this switch successfully. I am synced current in master branch in all layers as of today. The switch causes libtool link to fail due to missing libbz2.so. If I don’t specify the switch, the build completes without errors. It is important to be able to build poky linux with this switch to avoid certain crash conditions as described in the ARM errata document. Steve Pavao Korg R&D-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
