The typical approach for recipes which build proprietary code is to set LICENSE to "CLOSED" (and not define LIC_FILES_CHKSUM). I'm not sure what the advantages are of creating a license text for a pro

It's unconventional, but I guess it will work OK (i.e. it won't have any surprising or negative side effects). It's better than (for example) one recipe fetching source from the build directory of ano

A clearly internal proprietary image would remove the reference to oe-core from the image name, so "acme-image-minimal.bb" rather than "acme-core-image-minimal.bb". I don't know. Adding to the core im

Nothing clever going on, it's just a bug. In general, using /etc instead of ${sysconfdir} etc will appear to work fine until you add BBCLASSEXTEND and try to build <recipe>-native, at which point thin

It's an example of a "pure" toolchain recipe. You are free to modify it and add additional packages or use it as a reference to create your own toolchain recipe. Here's another example of a pure toolc

It's not related to other machines. There are other images which set QB_MEM to "-m 512" based on the opengl distro feature. If qemu-system-arm versatilepb can only support 256MB then these images need

The issue with pulseaudio has been discussed on the list and bugs have been raised upstream. It's due to pulseaudio's switch to meson (ie the autotools build still correctly detects ARM soft float, al

Grepping for QB_MEM suggests there are other images which need the same fix. Maybe good to fix all of them at once rather than one at a time.

Wouldn't "sidestep" be a more accurate description then "resolve" ? Either way I'm not sure that changing qemuarmv5 just to workaround one broken package is the right approach. Doesn't it mean OE will

<fransmeulenbroeks@...> wrote: Agreed. Adding a runtime dependency on util-linux-flock is the safest fix. For reference, there's a patch which does that here: https://github.com/lgirdk/meta-mng/

Busybox provides flock, but it doesn't support the -w option (wait with timeout). Either the util-linux flock is required or resolvconf needs to be patched to drop the -w option.

util-linux-flock has its own package. Patching resolvconf to use readlink -f (instead of readlink -m) should be sufficient to allow it to work with busybox readlink.

The memset() should be removed too.

Perhaps first decide what you are actually trying to do. The choice is between including debug symbols in the mongodb binary installed on the target (e.g. modifying INHIBIT_PACKAGE_STRIP and/or INHIBI

If the goal is to ensure that the optimisation flag from FULL_OPTIMIZATION and the -D_FORTIFY_SOURCE flag from lcl_maybe_fortify are always applied together then isn't the easiest solution to move -D_

<otavio.salvador@...> wrote: That's a concern if you're trying to create a package feed. But in that case you should already be taking care that BSP layers don't change the way recipes in

On Fri, Jan 29, 2021 at 12:34 AM Diego Santa Cruz via lists.openembedded.org <diego.santacruz=spinetix.com@...> wrote: MACHINE and DISTRO features are global variables which should

Doesn't look right. That forces the whole package to be compiled with floating point instructions, which will break targets which need soft float. Aside from the fact that the change itself looks wron

<richard.purdie@...> wrote: Does it? It just looks like an extension of a definition of PACKAGECONFIG but with the logic all reversed (e.g. instead of adding FOO to PACKAGECONFIG to en

The question is not whether start-stop-daemon supports using PID files but whether the busybox mdev application supports creating them. It looks like although most of the busybox daemons do, mdev does