[oe] [PATCH] drbd-utils: fix dependency for perl under small-fs

From: "Yadi.hu" Perl script drbd-overview fails to run due to some of perl's lib noexists under small rootfs,fixing it through adding explicit definitions Signed-off-by: Marius Tiplea Signed-off-by: Yadi.hu ---

[oe] drbd-utils: fix dependency for perl under small-fs

when run drbd-overview under samll fs, the perl script fails to run due to lack of perl's lib. warning shows as below: drbd-overview random: nonblocking pool is initialized Can't locate Getopt/Long.pm in @INC (you may need to install the Getopt::Long module) (@INC contains: /etc/perl

[oe] [meta-clang][PATCH] clang: update for cmake changes in oe-core

cmake.bbclass in oe-core master (soon to be Pyro) doesn't set CMAKE_CROSSCOMPILING unconditionally, but only when it's actually cross-compiling. This means the clang-native build doesn't think it's cross-compiling, so the recipe can be simplified. Signed-off-by: Ross Burton

[oe] [meta-oe][PATCH 2/2] opencv: disable broken Intel FP16 detection

With opencv-3.2, the configuration detects if the target supports half-precision floating-point format. This fails to compile for some Intel targets such as skylake with an error such as: error: '_mm_cvtph_ps' was not declared in this scope The configuration used to work in opencv-3.1 so

[oe] [meta-oe][PATCH 1/2] Revert "opencv: disable broken Intel FP16 detection"

This reverts commit 51fbd3cf7db14399bc1c69c4a5fd63f157fd209d. The long log was truncated due to a formatting error. Signed-off-by: Randy MacLeod --- .../0001-Revert-cuda-fix-fp16-compilation.patch| 27 --- ...vert-check-FP16-build-condition-correctly.patch |

Re: [oe] [meta-oe][PATCH] opencv: disable broken Intel FP16 detection

--- are normal separator of commit message, so all git handling tools would strip this as did patchwork as you can see: https://patchwork.openembedded.org/patch/139481/ I'm fine either way (leave the complete message only on ML or you sending new patch with fixed formatting and I'll apply it

Re: [oe] [meta-oe][PATCH] opencv: disable broken Intel FP16 detection

On 2017-04-26 09:33 PM, Randy MacLeod wrote: The configuration worked in opencv-3.1 so revert two commits to drop the FP16 detection even though it may make opencv slower. The only change in the configure log is: --- FP16: Compiler support is available +-- FP16: Compiler support is not available

[oe] [meta-networking][PATCH] wireguard: module install cleanup

The module_install target shouldn't be used, just installing the module to the sysroot directly seems more appropriate. Signed-off-by: Joe MacDonald --- .../wireguard/wireguard-module_0.0.20170421.bb | 20 ++-- 1 file changed, 14 insertions(+), 6

Re: [oe] [meta-networking][PATCH v3] wireguard: add WireGuard kernel module and tools

[Re: [oe] [meta-networking][PATCH v3] wireguard: add WireGuard kernel module and tools] On 17.05.01 (Mon 14:37) Stefan Agner wrote: > On 2017-05-01 08:18, Joe MacDonald wrote: > > [Re: [oe] [meta-networking][PATCH v3] wireguard: add WireGuard kernel > > module and tools] On 17.04.28 (Fri 18:18)

Re: [oe] cacao-native 1.6.1 failing because compiler not produced?

So my apologies for these messages I guess, but yeah. After linking a java executable Cacao-1.6.1 would build. After specifying GCCVERSION ?= "5.4.0" openjdk-7 would build. My little NAS device for which it was meant is too old though for the versions used. I have a toolchain for it but I