Re: [yocto] #yocto bootchooser: Cannot get state 'state'

Hi, Did you install the SDK? Did you run the environment script? make: /path/to/your/yocto/toolchain/bin/arm--linux-gnueabihf-gcc: Kommando nicht gefunden LEX scripts/kconfig/lexer.lex.c /bin/sh: 1: flex: not found YACCscripts/kconfig/parser.tab.h /bin/sh: 1: bison: not

Re: [yocto] Multiconfig question

Hi, Please see my comments in-line On 07/09/2020 17:53, Eil?s N? Fhlannag?in wrote: Assuming this: bitbake multiconfig:ConfigA:core-image-foo multiconfig:ConfigB:core-image-bar Is there a way during or before the rootfs of ConfigB:core-image-bar to tell what else was run during execution?

Re: [yocto] how does "bitbake meta-toolchain" map to a particular "image" when generating SDK?

Hi My comments are in-line On 05/07/2020 22:24, Robert P. J. Day wrote:   i'd assumed as much, but is there a reason that the meta-toolchain target is not mentioned at all in the SDK manual? Would that not be the right place to mention it, even briefly? I guess it depends on the

Re: [yocto] License reporting for golang (and rust)

Hi, My comments are in-line On 30/06/2020 14:37, Irving ST wrote: Hi, For anyone else having the same problem, here's what I eventually did for my go stuff: I created a bbclass containing a task that gets inherited by all packages, but the task only does some work when it detects that it is

Re: [yocto] License reporting for golang (and rust)

Hi, My comments are in-line On 22/06/2020 11:53, Irving ST wrote: Hello, I am building a device that uses some Go (and Rust) dependencies. This is on Yocto 2.7 / Warrior. I noticed that after building an image, the generated license.manifest and package.manifest (in tmp/deploy/licenses/)

Re: [yocto] Go toolchain in SDK

On 16/06/2020 23:55, Robert Berger via lists.yoctoproject.org wrote: bitbake core-image-sato-sdk -c populate_sdk and currently also for: bitbake core-image-sato-sdk -c populate_sdk_ext ... and no arm-resy-linux-gnueabi-go on the target, only on the host SDK I don't think that's the way

[yocto] Go toolchain in SDK

Hi, What is the "proper" way to add the Go toolchain to an SDK nowadays (dunfell)? I saw there is in poky: ./meta/recipes-core/meta/meta-go-toolchain.bb but I am not quite sure how to build an SDK with meta-go-toolchain included. so I added something like that to local.conf which seems to

Re: [yocto] Error when building eSDK for a `docker load`able tarball

Hi, And as far as I understand you tried to build some extensible SDK against an x86-64 container. Please note, that my SDK most likely contains a bit more than the "standard" stuff[0], but this should not make much of a difference here. [0]

Re: [yocto] Suggestions on improvements

Hi, On 08/01/2021 04:59, Meh Mbeh Ida Delphine wrote: > > Due to some mismatches, warnings pop up during the build. Below are some > few sample warnings and I'm aware of false positives; Why do you think they are false positives? > > WARNING: glibc-2.32-r0 do_package: License for package nscd

Re: [yocto] OpenEmbedded Virtual Stand at FOSDEM 2021

Hi, On 13/01/2021 23:33, Paul Barker wrote: Hi folks, * Any participants in the project who want to help host the Matrix chat room between 09:00 and 18:00 each day of the event. This will likely involve introducing the project to folks dropping in the chat who aren't familiar with

Re: [yocto] Points to consider while moving to new yocto versions

Hi, My comments are in-line On 25/01/2021 10:07, amaya jindal wrote: Hi All, We are planning to move to New yocto from current one that is krogoth yocto to some updated one. I would consider it "best practice" to somewhat try to stay up to date with recent yocto versions and plan for

Re: [yocto] 2038 time problem fix in yocto #kernel #linux #yocto #zeus

Hi, On 03/02/2021 09:13, dhandhukiya.par...@gmail.com wrote: Hi, We need to have a fix for 2038 problem for out 32 bit based product which is running Yocto (Linux). 2038 time problem was fixed in Linux kernel recently https://www.theregister.com/2020/10/19/linux_5_10_y2k38_fixes/ How about

Re: [yocto] Extensible SDK of core-image-minimal fails to install

Hi, On 12/06/2021 10:47, Richard Purdie wrote: I think it may be this bug: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14428 We don't have a fix as yet, it looks difficult to solve :( Cheers, Richard Not a fix, but a workaround, if you are willing to use containers is to create a

Re: [yocto] the downside of parallelism

Hi, On 20/06/2021 12:55, Robert P. J. Day wrote: refactoring existing (legacy) code base into more bite-sized bitbake recipes to speed up build by taking advantage of 6-core (12-thread) dell laptop ... end result is that i get so much parallelism that laptop shuts down from overheating.

Re: [yocto] Building eSDK fails #sdk

Hi, My comments are in-line On 04/02/2021 19:43, alexander.tr...@deveritec.com wrote: Hello, I build the SDK with bitbake core-image-base -c populate_sdk and it works just fine. But trying to build the eSDK with bitbake core-image-base -c populate_sdk_ext results in this error: ERROR:

Re: [yocto] [prelink-cross][PATCH] Add SPDX license headers to all source files

On 04/02/2021 19:17, Richard Purdie wrote: - GNU Lesser General Public - License as published by the Free Software Foundation; either - version 2.1 of the License, or (at your option) any later version. - +* SPDX-License-Identifier: GPL-2.0-or-later +*/ I guess the correct SPDX id is

Re: [yocto] #yocto #kernel setting up PREMIRRORS under zeus

Hi, Please see my comments in-line. On 24/01/2021 22:09, Robert P. J. Day wrote: On Sun, 24 Jan 2021, Monsees, Steven C (US) via lists.yoctoproject.org wrote: I added the following to my local.conf: INHERIT += "own-mirrors" SOURCE_MIRROR_URL = “file:///ede/tms/yocto/zeus/downloads/PATH”

Re: [yocto] bitbake controlling memory use

Hi, My comments are in-line. On 11/04/2021 18:23, Gmane Admin wrote: My build machine has 8 cores + HT so bitbake enthusiastically assumes 16. However I have (only?) 16GB of RAM (+24GB swap space). 16GB of RAM has always been more then enough with 4 core + HT, but now building certain

Re: [yocto] #golang: go fetches dependencies in compile phase

On 09/04/2021 16:53, Juergen Landwehr wrote: Hi, we are developing an application in go and use the "go-mod" bb-class from poky. This works fine. However, the problem is, that the dependencies in go.mod are now fetched in the compile phase and not in the fetch phase. Alexander (whom you

Re: [yocto] #golang: go fetches dependencies in compile phase

Hi, My comments are inline. On 12/04/2021 14:47, Juergen Landwehr wrote: Hi Robert, thanks for your thoughts. I see your point and the last thing I want is "NOT reproducable builds". But dependency management in go is not that arbitrary as it may seem. ... if everybody does what they are

Re: [yocto] Integrating Ubuntu 20.04 root file system in yocto for i.MX8M #yocto #kernel #linux

Hi, My comments are in-line. On 12/02/2021 14:30, Ross Burton wrote: The first question is why. It sounds like you want Ubuntu but the bootloader and kernel built by Yocto. I'm struggling to see what this would achieve. ... a legal battle maybe? Bring in the lawyers! I would also ask:

Re: [yocto] Regarding Mender integration

Hi, Please see my comments in-line. On 16/02/2021 19:48, U RAVI KUMAR wrote: I have some issues while integrating the mender on the yocto project.I have included meta-mener-core,meta-mender-raspberrypi layers.And iam getting the following error: ERROR: u-boot-1_2020.07-r0

Re: [yocto] [meta-virtualization]: dunfell docker run issues

Hi, On 04/02/2021 17:03, Marek Belisko wrote: Hi, I'm trying to run docker containers on orangepi and use meta-virtualization layer to add docker. I've installed the docker-ce package and everything seems to be fine. But docker service seems fails to start with: Feb 04 15:00:01 orange-pi-zero

Re: [yocto] Pyinstaller error in yocto #yocto

Hi, Please don't use screen shots, but pastebin instead. I already mentioned this on fb. My comments are inline. On 29/08/2021 13:48, yasminebenghoz...@gmail.com wrote: Hello, I successfully installed pyinstaller in my yocto image , but while executing the command it doesn't work It

Re: [yocto] Cannot build yocto anymore after updating all layers to current dunfell branch tips

On 14/08/2021 00:28, Manuel Wagesreither wrote: Hello all, I updated the layers of my project to the current dunfell branch tips. See here: https://gitlab.com/manuel_wagesreither/bora-proj/-/commit/de631634d7556987d2551d0cedca8f67530bc78d Since then, the build is failing with the following

Re: [yocto] [meta-security][PATCH 1/2] image-with-hardened-binaries: add class

Hi, On 21/08/2021 18:35, Armin Kuster wrote: Regarding the selftest, is there test for failure? I ran this against core-image-minimal and nothing was printed out. Does that mean its fine? You may want to remove the ".py" from python3-checksec.py-native_0.6.1.bb, its not needed. If you run

Re: [yocto] Install SDK with yocto

Hi, After you download e.g. the tarball, you'll find an installation guide inside. It says: OpenSUSE 13.1 / 42.3 Ubuntu ® 14.04 / 16.04 Fedora 26 / 27 Debian 8.10 / 9.3 So I am not sure why you assume that this should work out of the box/at all with the Yocto Project. If you really want

Re: [yocto] #dunfell Path to sources in debugfs

Hi, My comments are inline. On 05/10/2021 17:04, bohdan.shubenok@sigma.software wrote: Hi all, I`m trying to debug coredump generated on embedded system running dunfel. Just to clarify your user space applications crashes and you try to see why? In other words you would like to load the

Re: [yocto] #yocto -third party licensimg

Hi Steven, Please see my comments inline On 24/09/2021 14:10, Monsees, Steven C (US) via lists.yoctoproject.org wrote: The one solution I found says : Add *LICENSE_PATH += "${LAYERDIR}/custom-licenses"* under conf/layer.conf, *this does not resolve this warning*. This is a new item being

Re: [yocto] [poky] [PATCH] local.conf.sample: disable prelink

Hi Alex, RP, Mark, I did some research on the subject in order to try to figure out what is going on. 1) I come to a similar conclusion with what found, but tried to look a bit deeper for the reason. 1.1) The reason that cross-prelink is not prelinking is, that for a quite some time by

Re: [yocto] [poky] [PATCH] local.conf.sample: disable prelink

On 22/07/2021 22:05, Alexander Kanavin wrote: PIE is nowadays more or less the only available option and is expected for improved security; Yocto does not even test non-PIE builds or provide an off the shelf way to turn it off. I am worried about those libraries, which are non-PIE libraries

Re: [yocto] Additional hardening options

Hi, This[1] is what I usually add as well to the security flags. With respect to the "default" flags I had some fun with the SDK and  -D_FORTIFY_SOURCE=2 and -fstack-protector-strong. I guess they do have some performance impact as well, but I did not do very thorough research. Also, I did

Re: [yocto] [Question] How to handle GPLv3 packages?

t;car" you have an expensive eval board afterwards. Another interesting issue is the "EU Radio Equipment Directive". It seems to be incompatible with GPLv3[1] ;) [1] https://fsfe.org/activities/radiodirective/radiodirective.en.html Regards,     Matthias -- Robert Berger Embedded