I tweaked the recipe a bit (you should use SRCREV, versus a tag), etc, and added some link flags to make things static. This tends to be why I write my own do_compile for go applications, so I can

Sure here you go: ``` SUMMARY = "easyjson" DESCRIPTION = "easy json command util" HOMEPAGE = "https://github.com/mailru/easyjson" LICENSE = "MIT" LIC_FILES_CHKSUM =

Signed-off-by: Khem Raj <raj.khem@...> --- recipes-devtools/flex/flex_%.bbappend | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 recipes-devtools/flex/flex_%.bbappend diff --git

This patch updates SRC_URIs using git to include branch=master if no branch is set and also to use protocol=https for github urls as generated by the conversion script in OE-Core. Signed-off-by:

Well it turns out that following the Perf recipe was not only a good idea, but absolutely necessary. The perf recipe copies the code out of the work-shared kernel directory into the perf build

It varies based on the application, the ones I've dealt with, tend to have a -static flag. Of course, the flag may not be exposed, and in those scenarios, I patch the Makefile/build. If you have

Yep might be… For me that’s desirable as these a built-utils, it’s golang and I see no benefit in having them dynamically linked anyay. Any tips how to statically link these? As far as I

I'd bet it is a variant of this: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14386 Bruce -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the

Here some outputs: Bitbake -c devshell target-recipe sh-4.4# easyjson Segmentation fault sh-4.4# strace

There is literaly no stacktrace just a segmentation fault pretty early in the execution (like 3rd instruction or something). I will send more outputs as soon as my dual-core has finished compiling

Merged.

do you have stack trace ? that might give some more info on whats going on

Ensure that selinuxfs is mounted using the noxec and nosuid flags. The current master branch of meta-selinux already contains this commit. Change-Id:

Hi yoto-devs/users, in order to get a golang application to run which relies on `go generate` calls I wrote special recipes for this tools and include them in my original recipe. However I always get

Fixes: ERROR: python3-fail2ban-0.11.2-r0 do_package_qa: QA Issue: python3-fail2ban installs files in /run, but it is expected to be empty [empty-dirs] Signed-off-by: Armin Kuster

Signed-off-by: Armin Kuster <akuster808@...> --- recipes-security/bastille/bastille_3.2.1.bb | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) diff --git

/var/log is normally a link to /var/volatile/log and /var/volatile is a tmpfs mount. So anything created in /var/log will not be available when the tmpfs is mounted. [Thanks to Peter Kjellerstedt for

A build flagged for QA (yocto-3.3.4.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.3.4.rc1 Build hash information: bitbake:

Update SRC_URIs using git to include branch=master if no branch is set and also to use protocol=https for github urls. Signed-off-by: Yi Zhao <yi.zhao@...> ---

This file is not needed anymore as bind daemon will create them by itself. Signed-off-by: Yi Zhao <yi.zhao@...> --- recipes-connectivity/bind/bind_selinux.inc | 7 -------