|
Re: Conditionally install files depending on locale
Scott Weaver
You might consider creating a custom task in your recipe where you can
toggle quoted messageShow quoted text
handle your unique requirements. https://www.yoctoproject.org/docs/latest/bitbake-user-manual/bitbake-user-manual.html#tasks Scott
On Mon, May 31, 2021 at 3:58 PM Amr Bekhit <amr@helmpcb.com> wrote:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Recipe for include-what-you-use and rpath problem
#sdk
Francesco Cusolito
Good morning everybody, I would like to include IWYU in my SDK, but I couldn't find a recipe, so I'm trying to write my own. LICENSE = "NCSA"
LIC_FILES_CHKSUM = "file://LICENSE.TXT;md5=59d01ad98720f3c50d6a8a0ef3108c88 \
file://iwyu-check-license-header.py;md5=cdc4ab52c0b26e216cbf434649d30403"
SRC_URI = "git://github.com/include-what-you-use/include-what-you-use.git;protocol=https;branch=clang_10"
PV = "0.14+git${SRCPV}"
SRCREV = "0.14"
S = "${WORKDIR}/git"
DEPENDS = "clang"
inherit cmake python3native
BBCLASSEXTEND_append = " \
nativesdk \
"
The application seems to compile fine, but in ERROR: nativesdk-include-what-you-use-0.14+git999-r0 do_package: chrpath command failed with exit code 7: /build/archimede/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-include-what-you-use/0.14+git999-r0/package/opt/Delcon/sdk/delconos-archimede-raspberrypi3-64/sysroots/x86_64-pokysdk-linux/usr/bin/include-what-you-use: RPATH=$ORIGIN/../lib:/build/archimede/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-include-what-you-use/0.14+git999-r0/recipe-sysroot/opt/Delcon/sdk/delconos-archimede-raspberrypi3-64/sysroots/x86_64-pokysdk-linux/usr/lib new rpath '$ORIGIN/../lib:$ORIGIN/../../../../../../../../build/archimede/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-include-what-you-use/0.14+git999-r0/recipe-sysroot/opt/Delcon/sdk/delconos-archimede-raspberrypi3-64/sysroots/x86_64-pokysdk-linux/usr/lib' too large; maximum length 220 ERROR: Logfile of failure stored in: /build/archimede/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-include-what-you-use/0.14+git999-r0/temp/log.do_package.1595 ERROR: Task (virtual:nativesdk:/build/archimede/workspace/recipes/include-what-you-use/include-what-you-use_git.bb:do_package) failed with exit code '1' NOTE: Tasks Summary: Attempted 1033 tasks of which 1024 didn't need to be rerun and 1 failed. You can see full The problem seems to be similar to the one reported on How can I resolve this
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Move of official IRC channels to libera.chat
Dear all,
As some of you may have read over the past days, there has been an ownership dispute over the freenode.net network. The IRC network has been used by the Yocto Project and many other projects over the past decades as a platform for discussion and support. The dispute led to the exodus of most former freenode staff from the network and the founding of a new network: libera.chat [1]. Starting today, the Yocto Project is migrating the official IRC channels from freenode.net to libera.chat. Everyone is encouraged to join #yocto on libera.chat, and get their nick registered on the new network as soon as possible. It's a soft migration, we don't expect to kick users from #yocto on freenode anytime, unless things go really bad on freenode. However we encourage everyone to move to libera.chat and *leave* the freenode channels during the next few weeks. We understand it will take some time to finalize the transition of all users, it is very important that we don't leave any member from our community behind during this transition. The Yocto Project community website was updated with all the information mentioned here, and can be found at [2]. We thank the freenode community for the many years of great service and collaboration, IRC has been, and will remain a key communication medium for our community! In addition, on popular demand, the Yocto Project can also be found on the Open Matrix Network, in the dedicated room called #yoctoproject:matrix.org, which can be accessed using [3]. Note that this Matrix room is bridged to the #yocto channel on Libera.chat, enabling full two-way communication between IRC and Matrix users. It is worth mentioning that OpenEmbedded has engaged in a similar transition, and users are encouraged to join #oe on libera.chat (or the OpenEmbedded Room on the Open Matrix Network [4]). In case of any difficulty , please reach out to me, Michael, Jan-Simon, Khem or Philip! cheers nico [1] https://libera.chat/ [2] https://www.yoctoproject.org/community/mailing-lists/ [3] https://matrix.to/#/#yoctoproject:matrix.org [4] https://matrix.to/#/#oe:matrix.org
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[ANNOUNCEMENT] Yocto Project 3.1.8 (dunfell-23.0.8) is Released
Vineela
Hello,
We are pleased to announce the Yocto Project 3.1.8 (dunfell-23.0.8) Release is now available for download.
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.8/poky-dunfell-23.0.8.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-3.1.8/poky-dunfell-23.0.8.tar.bz2
A gpg signed version of these release notes is available at:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.8/RELEASENOTES
Full Test Report:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.8/testreport.txt
Thank you for everyone's contributions to this release.
Vineela Tummalapalli Yocto Project Build and Release
- -------------------------- yocto-3.1.8 Release Notes - --------------------------
- -------------------------- Repositories/Downloads - --------------------------
Repository Name: poky Repository Location: https://git.yoctoproject.org/git/poky Branch: dunfell Tag: yocto-3.1.8 Git Revision: 6ebb33bdaccaeadff0c85aab27acf35723df00d8 Release Artefact: poky-dunfell-23.0.8 sha: 3ca4775bec270eae7d30bf290db42d918378891ba1be6026f30f6bc245be60e4 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.8/poky-dunfell-23.0.8.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-3.1.8/poky-dunfell-23.0.8.tar.bz2
Repository Name: openembedded-core Repository Location: https://git.openembedded.org/openembedded-core Branch: dunfell Tag: 2020-04.8-dunfell Git Revision: ecd636154e7cfc1349a7cfd8026a85eafa219535 Release Artefact: oecore-dunfell-23.0.8 sha: bf986f379fe1e038ccff49aee6f85e7006758738cddd916eb8dd3032a981c929 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.8/oecore-dunfell-23.0.8.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-3.1.8/oecore-dunfell-23.0.8.tar.bz2
Repository Name: meta-mingw Repository Location: https://git.yoctoproject.org/git/meta-mingw Branch: dunfell Tag: yocto-3.1.8 Git Revision: 524de686205b5d6736661d4532f5f98fee8589b7 Release Artefact: meta-mingw-dunfell-23.0.8 sha: 1c9f7ba3e9dba8ceb8155890c7365af6fc6486e54fba4aa3fb8032f6ea494bdb Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.8/meta-mingw-dunfell-23.0.8.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-3.1.8/meta-mingw-dunfell-23.0.8.tar.bz2
Repository Name: meta-gplv2 Repository Location: https://git.yoctoproject.org/git/meta-gplv2 Branch: dunfell Tag: yocto-3.1.8 Git Revision: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac Release Artefact: meta-gplv2-dunfell-23.0.8 sha: 8106a9651a4d1a111f7922557d56898a00a6c1c88c80477997bf5a38a16fd208 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.8/meta-gplv2-dunfell-23.0.8.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-3.1.8/meta-gplv2-dunfell-23.0.8.tar.bz2
Repository Name: bitbake Repository Location: https://git.openembedded.org/bitbake Branch: 1.46 Tag: 2020-04.8-dunfell Git Revision: 078f3164dcb1de7a141bec3a8fd52631d0362631 Release Artefact: bitbake-dunfell-23.0.8 sha: 888ada8f64b94d03c430fcf309e994ed0bd96ff09d4909aacc0706e0cf8c8659 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.8/bitbake-dunfell-23.0.8.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-3.1.8/bitbake-dunfell-23.0.8.tar.bz2
Repository Name: yocto-docs Repository Location: https://git.yoctoproject.org/git/yocto-docs Branch: dunfell Tag: yocto-3.1.8 Git Revision:09b64a4d246bdcca62dddee152deef7b0dea69d7
- ------------ Contributors - ------------ Alexander Kanavin Anatol Belski Anuj Mittal Bruce Ashfield Chen Qi Christophe Chapuis Diego Sueiro Douglas Royds Gavin Li Guillaume Champagne Jose Quaresma Joshua Watt Kai Uwe Broulik Khem Raj Konrad Weihmann Lee Chee Yang Marek Vasut Mark Hatle Michael Opdenacker Mike Crowe Mikko Rapeli Mingli Yu Niels Avonds Peter Budny Peter Morrow Reto Schneider Richard Purdie Robert P. J. Day Romain Naour Ross Burton Stefan Ghinea Steve Sakoman Vinay Kumar Yanfei Xu Yann Dirson Yi Fan Yu Zhang Qiang zhengruoqin
- --------------- Known Issues - --------------- Intermittent Failure in ptest : strace.printstrn-umoven.gen.test
- --------------- Security Fixes - --------------- db: update CVE_PRODUCT avahi: Exclude CVE-2021-26720 from cve-check librsvg: Exclude CVE-2018-1000041 from cve-check coreutils: Exclude CVE-2016-2781 from cve-check tiff: Exclude CVE-2015-7313 from cve-check bluez: Exclude CVE-2020-12352 CVE-2020-24490 from cve-check ghostscript: Exclude CVE-2013-6629 from cve-check cpio: Exclude CVE-2010-4226 from cve-check unzip: Exclude CVE-2008-0888 from cve-check openssh: Exclude CVE-2008-3844 from cve-check openssh: Exclude CVE-2007-2768 from cve-check logrotate: Exclude CVE-2011-1548,1549,1550 from cve-check jquery: Exclude CVE-2007-2379 from cve-check qemu: Exclude CVE-2018-18438 from cve-check qemu: Exclude CVE-2007-0998 from cve-check qemu: Exclude CVE-2017-5957 from cve-check builder: whitelist CVE-2008-4178 (a different builder) libnotify: whitelist CVE-2013-7381 (specific to the NodeJS bindings) cairo: backport patch for CVE-2020-35492 glibc: Document and whitelist CVE-2019-1010022-25 tiff: fix CVE-2020-35523 CVE-2020-35524 qemu: fix CVE-2021-3392 subversion: fix CVE-2020-17525 binutils: fix CVE-2021-3487 tar: Fix CVE-2021-20193 Binutils: Fix CVE-2021-20197 wpa-supplicant: fix CVE-2021-30004 curl: Patch CVE-2021-22876 & CVE-2021-22890
- --------------- Fixes - --------------- build-appliance-image: Update to dunfell head revision poky.conf: Bump version for 3.1.8 release poky.conf: Add fedora33 as a supported distro documentation: prepare for 3.1.8 release ref-system-requirements.rst: Add Fedora 33 to list of supported distros sstate: Handle manifest 'corruption' issue boost: fix do_fetch failure Revert "cml1.bbclass: Return sorted list of cfg files" bitbake: providers: selected version not available should be a warning meta/lib/oe/rootfs.py: Fix typo "Restoreing" -> "Restoring" image.bbclass: fix comment "pacackages" -> "packages" dejagnu: needs expect at runtime linux-yocto/5.4: qemuppc32: reduce serial shutdown issues linux-firmware: include all relevant files in -bcm4356 linux-firmware: upgrade 20210208 -> 20210315 lsb-release: fix reproducibility failure oeqa/qemurunner: Improve handling of run_serial for shutdown commands oeqa/qemurunner: Fix binary vs str issue oeqa/qemurunner: Improve logging thread exit handling for qemu shutdown test python3-jinja2: 2.11.2 -> 2.11.3 poky-tiny.conf: set PREFERRED_VERSION_linux-yocto-tiny to 5.4% reproducible.py: add quilt-ptest and valgrind-ptest ovmf: update edk2-stable202005 -> edk2-stable202008 ovmf: update to 202005 ovmf: update to 202002 lib/package_manager: Use shutil.copy instead of bb.utils.copyfile for intercepts libevent: Increase ptest timing tolerance 50 ms -> 100 ms sanity.bbclass: mention CONNECTIVITY_CHECK_URIS in network failure message classes/image: Use xargs to set file timestamps Revert "oeqa: Set LD_LIBRARY_PATH when executing native commands" diffoscope: add native libraries to LD_LIBRARY_PATH make-mod-scripts: add HOSTCXX definitions and gmp-native dependency perf: fix python-audit RDEPENDS cml1.bbclass: Return sorted list of cfg files rootfs.py: find .ko.gz and .ko.xz kernel modules as well pybootchart/draw: Avoid divide by zero error gstreamer1.0-plugins-good: on wayland qt5 needs qtwayland kernel.bbclass: Remove do_install[prefunc] no longer needed ptest-runner: libgcc must be installed for pthread_cancel to work linux-yocto/5.4: update to v5.4.116 linux-yocto/5.4: update to v5.4.114 wireless-regdb: upgrade 2020.11.20 -> 2021.04.21 yocto-uninative: Update to 3.1 which includes a patchelf fix bitbake: fetch/gitsm: Fix crash when using git LFS and submodules bitbake: runqueue: Fix deferred task issues bitbake: bitbake: tests/fetch: remove write protected files too bitbake: bitbake: tests/fetch: fix test execution without .gitconfig license_image.bbclass: Fix symlink to generic license files license_image.bbclass: Detect broken symlinks linux-firmware: Package RSI 911x WiFi firmware yocto-check-layer: Avoid bug when iterating and autoadding dependencies kernel.bbclass: Configuration for environment with HOSTCXX meta/lib/oeqa/core/tests/cases/timeout.py: add a testcase for the previous fix oeqa: tear down oeqa decorators if one of them raises an exception in setup oeqa/selftest/bblayers: Add test case for bitbake-layers layerindex-show-depends cve-update-db-native: skip on empty cpe23Uri linux-yocto/5.4: fix arm defconfig warnings linux-yocto/5.4: update to v5.4.112 linux-yocto/5.4: update to v5.4.111 linux-yocto/5.4: update to v5.4.109 ca-certificates: Fix openssl runtime cert dependencies parselogs: ignore floppy error on qemu-system-x86 at boot stage groff: not ship /usr/bin/grap2graph libtool: make sure autoheader run before automake kmod: do not symlink config.guess/config.sub during autoreconf pseudo: Upgrade to add trailing slashes ignore path fix lib/oe/terminal: Fix tmux new-session on older tmux versions (<1.9) sanity: Further improve directory sanity tests sanity: Add error check for '%' in build path insane: clean up some more warning messages oeqa/selftest: Ensure packages classes are set correctly for maintainers test oeqa/selftest: Hardcode test assumptions about heartbeat event timings externalsrc: Detect code changes in submodules Revert "externalsrc: Detect code changes in submodules" go_1.14: don't set -buildmode=pie when building for windows targets goarch: map target os to windows for mingw* TARGET_OS image-live.bbclass: optional depends when ROOTFS empty diffoscope: Upgrade 168 -> 172 diffoscope: Upgrade 136 -> 168 selftest/reproducible: Sort the unused exclusion list selftest/reproducible: track unusued entries in the exclusion list selftest/reproducible: adjust exclusion list for dunfell selftest/reproducible: add an exclusion list for items that are not yet reproducible selftest/reproducible: enable world reproducibility test
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: systemd, ELF binaries and runtime dependency tracking
Luca Bocassi
On Tue, 2021-06-01 at 09:23 -0700, Khem Raj wrote:
Yeah, I was thinking of starting from the systemd recipe only. Given the project has to add support for it, a distro-wide rollout wouldn't make much sense anyway. -- Kind regards, Luca Boccassi
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: How to switch yocto INIT_MANAGER from systemd to sysvinit
#dunfell
Swapna Nannapaneni
Example helps. Thanks!!
On Mon, May 31, 2021 at 2:05 AM Zoran <zoran.stojsavljevic@...> wrote: What about the following:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: systemd, ELF binaries and runtime dependency tracking
On 6/1/21 9:13 AM, Luca Boccassi wrote:
On Tue, 2021-06-01 at 07:58 -0700, Khem Raj wrote:right and thats why I will be reluctant to go too far at distro level unless there is general interest in wider communities as it can make us an island.Yes ideally ELF shared objects/the linker/the loader would support weak There have been lots of theoretical discussions about pros and cons,you could tool it as a packageconfig for systemd alone and run with it and see how it pans out. So leaving aside other distros, is this something that would concretelywe could certainly try that, provided systemd upstream is supportive of it.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: systemd, ELF binaries and runtime dependency tracking
Luca Bocassi
On Tue, 2021-06-01 at 07:58 -0700, Khem Raj wrote:
Yes ideally ELF shared objects/the linker/the loader would support weak symbols (like dylib on OSX). Unfortunately they do not, and it seems there's no interest to add it becasue there's no concrete use case that shows it's useful. But that cannot happen until there's some support for it. Chicken and egg... There have been lots of theoretical discussions about pros and cons, and my hope was that if at least one distro could find it useful, and could show that it is in practice useful and the theoretical issues are not that problematic and could be solved, others would follow suit. So leaving aside other distros, is this something that would concretely benefit the Yocto project for handling the systemd recipe? There are currently 12 dlopen()-based optional dependencies in systemd, and the number grows with each release. -- Kind regards, Luca Boccassi
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Yocto Technical Team Minutes, Engineering Sync, for June 1 2021
Trevor Woerner
Yocto Technical Team Minutes, Engineering Sync, for June 1 2021
archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == disclaimer == Best efforts are made to ensure the below is accurate and valid. However, errors sometimes happen. If any errors or omissions are found, please feel free to reply to this email with any corrections. == attendees == Trevor Woerner, Stephen Jolley, Colin McAllister, Armin Kuster, Joshua Watt, Steve Sakoman, Saul Wold, Richard Purdie, Philip Ballister, Bruce Ashfield, Randy MacLeod, Michael Ambrus, Michael Halstead, Daiane Angolini, Peter Kjellerstedt, Trevor Gamblin, Ross Burton, Tim Orling, Alexandre Belloni, Jan-Simon Möller, Scott Murray, Tony Tascioglu == notes == - 3.4 M1 (honister) to be built next week - 3.1.8 (dunfell) passed QA, waiting final approval for release - CVE issue count: master=6, hardknott=14 - AUH to run more regularly - multiconfig issues still not ironed out - ptest based on core-image-minimal instead of core-image-sato - record high levels of AB intermittent issues == general == RP: AB int issues seemed to be helped by limited the number of threads used for compression RP: two cases of trying to talk to upstream but found problems with our logging, upstream says “go away and fix your logging” before we can continue discussions PeterK: question about yocto-poky tags RP: we stopped adding “hardknott-pokyversion” (e.g. “hardknott-25.0”) tags and this broke PeterK’s workflow. i would prefer to move away from these tags and use yocto tags instead PeterK: i’m okay moving to something new. “hardknott-3.3.1” would be better than “hardknott-25.0”. also, could we wait and not change this in the middle of a release series? (i.e. wait for the first release of honister). RP: i need to talk to MichaelH and Vineela and figure something out RP: this is part of a larger task to rationalize the release process a bit better (e.g. also need to tie in the documentation releases too with Nico) RP: this tells us that people are using some of these things that we didn’t think were being used MichaelH: Vineela and I have a couple other release things we need to go over, i’ll make a meeting. we could add tags going backwards so we can transition now. this would give us some correlation to the tags in openembedded etc TimO: freenode? RP: we didn’t do anything last week (due to Summit). i think Nico needs to coordinate with MichaelH. i believe we are moving over to libera.chat Scott: fd.o seems to have moved to OFTC TrevorW: do we have ops in #yocto and #oe? RP: yes TimO + PhilipB: we’ve got slack too JPEW: matrix integration too? TimO: yes Jan-Simon JPEW: SBOM RP: please discuss on licensing email list RP: i think there’s a plugfest going on and i don’t think anyone from YP has signed up Randy: Mark from WR is attending RP: i’d like to fly the YP flag there JPEW: details? RP: https://docs.google.com/forms/d/e/1FAIpQLSdVOewc3uCZh39inX4X7QsA_jaQMqyrEiLFrWEZEpWxRCi3eQ/viewform Philip: who’s interested in showing up at the plugfest? JPEW: i would, but 22nd doesn’t work for me Philip: i could go ??: what’s the layer? Saul: meta-doubleopen Ross: 22 doesn’t work for me either, but i could help put stuff together beforehand TrevorW: videos for YPS are up https://www.youtube.com/playlist?list=PLD4M5FoHz-TwWYbaJwduH8ZYNYvva76QQ https://elinux.org/YPS_May2021_Presentations Jan-Simon: what’s the procedure for updating layerindex? RP: PaulE is an admin Ross: I was added recently RP: MichaelH who are the admins? MichaelH: myself, PaulE, Ross, JaMa, Nico, Randy TimO: PaulE recently added me too J-S: there are a lot of issues with the layerindex (e.g. emails bouncing) Randy: should we move the next monthly meeting to avoid the 4th of July? RP: sounds good, we’ll move it to July 13th
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: systemd, ELF binaries and runtime dependency tracking
On 5/31/21 3:40 PM, Paul Eggleton wrote:
Hi folksFinding dlopen dependencies is a neat idea, but it has to be accepted cross distro, and also applications have to manually declare it in code if I understand systemd's patch correctly. This will be hard to accomplish as you can see changes are spread across apps from distro point of view. Perhaps there is a smarter way of detecting adding them in ELF spec itself and then have tools like linker help implement this and also possibly collect the information or guide the users to achieve this would be helpful. Cheers
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Yocto Project Status WW22`21
Stephen Jolley
Current Dev Position: YP 3.4 M1 Next Deadline: 7th June 2021 YP 3.4 M1 build
Next Team Meetings:
Key Status/Updates:
We are working to identify the load pattern on the infrastructure that seems to trigger these.
Ways to contribute:
YP 3.4 Milestone Dates:
Planned upcoming dot releases:
Tracking Metrics:
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at: https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am on the first Tuesday (PDT)
Stephen Jolley
All,
Just a reminder we will hold the monthly Yocto Project Technical Meeting at 8am PST tomorrow. (6/1)
Yocto Project Technical Team Meeting: We encourage people attending the meeting to logon and announce themselves on the Yocto Project IRC chancel during the meeting (optional): Yocto IRC: http://webchat.freenode.net/?channels=#yocto
Wiki: https://www.yoctoproject.org/public-virtual-meetings/
When Monthly from 8am to 9am on the first Tuesday Pacific Time Where Zoom Meeting: https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
We are tracking the minutes at: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit?pli=1 Please request access if you want to assist in editing them. The world should have view access.
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
systemd, ELF binaries and runtime dependency tracking
Paul Eggleton <paul.eggleton@...>
Hi folks
Upstream in the systemd project, a proposal has been made to add a special section to output ELF binaries to record soft runtime dependencies, so that they could be read and utilised by distribution build systems such as ours (they would be translated into RRECOMMENDS in our case). At the moment that doesn't seem to have generated a huge amount of interest in the traditional distro space, but would it be interesting for us? https://github.com/systemd/systemd/pull/17416 For clarity, we (Microsoft) will volunteer to do the integration assuming the above pull request gets reopened and merged, which is more likely if we express our interest. Cheers Paul
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
M+ & H bugs with Milestone Movements WW22
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Enhancements/Bugs closed WW22!
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Current high bug count owners for Yocto Project 3.4
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Yocto Project Newcomer & Unassigned Bugs - Help Needed
Stephen Jolley
All,
The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading: https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project. If anyone can help, please take ownership of the bug and send patches! If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.
Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 353 unassigned or newcomer bugs.
We're hoping people may be able to spare some time now and again to help out with these. Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system. There are also roughly four different "priority" classes right now, “3.2”, “3.3, "3.99" and "Future", the more pressing/urgent issues being in "3.2" and then “3.3”.
Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account). The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Bitbake failure
Cris Scott
Not sure who to ask about this. Using https://push.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-extended/lighttpd/lighttpd_1.4.59.bb to build lighttpd, bitbake fails, and I receive tons of messages that look like:
ERROR: lighttpd-1.4.59-r0 do_package_qa: QA Issue: /usr/lib/mod_staticfile.so contained in package lighttpd-module-staticfile requires libc.so.6(GLIBC_2.4), but no providers found in RDEPENDS_lighttpd-module-staticfile? [file-rdeps]
Can someone point me in the right direction to resolve this?
-Bill
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
kernel init debug features
Monsees, Steven C (US)
I have kernels based off “rocko” and “zeus” for both Arm and Intel… all using sysvinit (not systemd).
Under the Yocto build system, how can I easily set the following kernel configuration variables based on the build for testing/debug ?
· sched_rt_period_us · sched_rt_runtime_us · overcommit_memory
thanks, Steve
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Conditionally install files depending on locale
Hello,
I'm trying to put together a recipe where I conditionally install files depending on the image locale. I can see from the reference manual that Yocto will use the contents of IMAGE_LINGUAS to install locales during the root filesystem construction process. How can I go about creating locales for my custom packages/recipes?
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|