Hi, My comments are inline. I am not a lawyer, but I guess you could mention in your manual that you can dish out a non reversible image which was built with a "dummy" key. This would allow the end cu

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 h

Hi, My comments are inline. Just to clarify your user space applications crashes and you try to see why? In other words you would like to load the application and the core file into your debugger and

#dunfell

Hi Steven, Please see my comments inline wrote: I am a bit confused, but can try to show you what I typically do. In my custom meta-my-layer I add to layer.conf: #--> LICENSE_PATH += " ${LAYERDIR}/cus

#yocto

Hi, Please don't use screen shots, but pastebin instead. I already mentioned this on fb. My comments are inline. It misses ldd. It's here: https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/rec

#yocto

Hi, If you run checksec manually against some binary e.g. ls.coreutils it outputs something like this: https://pastebin.com/JkeN1h3k Not sure what this should output.

There was an OVERRIDE syntax change and this is what are seeing. Some layers, like meta-openembedded incorporated this change into their master branch. So either you need to update all your layers as

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

I am worried about those libraries, which are non-PIE libraries by default. My theory is, that they are non-PIE since prelink is able to operate on them. So prelink can "at least" be used a PIE detect

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.

Hi, Sorry for my stupid question;) If you have 12 threads, it's 12 threads and not more. I guess there needs to be some kind of dependency between your new recipes. make -j can use as many cores as yo

Hi, Not a fix, but a workaround, if you are willing to use containers is to create a build container and a similar sdk container. I added more information to the bug above. Regards, Robert

Hi, My comments are inline. ... if everybody does what they are supposed to - which is not the case. This does not sound too bad. This would also mean, that if the outside repo dies you can still buil

Alexander (whom you cc'ed here as well) wrote a long time ago on the mailing list[1] about this stuff. We have a couple of issues with those "modern" languages like go, which behave quite differently

Hi, My comments are in-line. The RAM usage depends heavily on what you are building ;) - It could be some crazy C++ stuff ;) Is Linux your build host? Then you can use cgroups to limit resources like

Hi, Please see my comments in-line. ... This looks like the patch you/mender try/tries to apply does not work with your u-boot version.[0] [0] https://github.com/mendersoftware/meta-mender/tree/master

Hi, My comments are in-line. ... a legal battle maybe? Bring in the lawyers! I would also ask: "What is your use case?" "Did you ask Canonical?" "Does Canonical allow you to do this?" From [1]: "Copyr

#linux #yocto #kernel

Hi, Can you please tell us which version of yocto this is? Also which kernel and especially which kernel config. I use something pretty recent (master kind of) and I am able to start docker and podman

I guess the correct SPDX id is then: LGPL-2.1-or-later In order to get this right I would highly recommend to use fossology to look at those files. Regards, Robert > > > > >

Hi, My comments are in-line Which version is this? Can it be reproduced? If so you might want to add it to https://bugzilla.yoctoproject.org Regards, Robert > > > >

#sdk