Hello!
On Wed, 13 Mar 2019 at 11:58, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Wed, Mar 13, 2019 at 08:14:29AM -0700, Greg Kroah-Hartman wrote:
On Wed, Mar 13, 2019 at 07:44:34AM -0700, Guenter Roeck wrote:
On Tue, Mar 12, 2019 at 10:09:18AM -0700, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.163 release. There are 96 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Thu Mar 14 17:10:06 UTC 2019. Anything received after that time might be too late.
Early results:
Building x86_64:tools/perf ... failed
Error log: Warning: arch/x86/include/asm/cpufeatures.h differs from kernel Warning: arch/x86/include/uapi/asm/kvm.h differs from kernel PERF_VERSION = 4.9.162.g605129 builtin-trace.c: In function ‘perf_evlist__add_vfs_getname’: builtin-trace.c:2071:8: error: implicit declaration of function ‘strstarts’ [-Werror=implicit-function-declaration] builtin-trace.c:2071:3: error: nested extern declaration of ‘strstarts’ [-Werror=nested-externs]
Also affects v4.4.y-queue.
Hm, at first I was worried about my backport, but if it hit 4.4 as well, that's not my fault :)
I'll look at this after breakfast, thanks!
I can't even get perf to build without any stable queue patches for 4.9.y at the moment, nor for 4.4.y, so something is odd, or I just have too "new" of a system. Let me go dig up a debian box to see if I can at least find a way to start to reproduce this...
Interesting. To add to the fun, just yesterday I tried building the Perf recipe from OpenEmbedded and it failed for these combinations: * 4.4.176 and x86_64: | CC /srv/oe/build/tmp-lkft-glibc/work/intel_corei7_64-linaro-linux/perf/1.0-r9/perf-1.0/bench/mem-memcpy-x86-64-asm.o | bench/mem-memcpy-x86-64-asm.S:4:10: fatal error: ../../../arch/x86/lib/memcpy_64.S: No such file or directory | #include "../../../arch/x86/lib/memcpy_64.S" | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | compilation terminated.
* 4.14.105 and i386: | In file included from util/libunwind/x86_32.c:33:0: | util/libunwind/../../arch/x86/util/unwind-libunwind.c: In function 'libunwind__x86_reg_id': | util/libunwind/../../arch/x86/util/unwind-libunwind.c:110:11: error: 'EINVAL' undeclared (first use in this function); did you mean 'UNW_EINVAL'? | return -EINVAL; | ^~~~~~ | UNW_EINVAL
Other combinations that worked: * 4.4.176 with arm, arm64, i386 * 4.9.162 with arm, arm64, i386, x86_64 * 4.14.105 with arm, arm64, x86_64 * 4.19.28 with arm, arm64, i386, x86_64 * 4.20.15 with arm, arm64, i386, x86_64 * 5.0.1 with arm, arm64, i386, x86_64
I'll try again the failing combos to discard a problem with the OE build itself.
Greetings!
Daniel Díaz daniel.diaz@linaro.org