- User Since
- Sep 2 2017, 9:44 AM (67 w, 36 m)
Tue, Dec 11
Thu, Dec 6
still get a warning during compile and then failure in the linking with the fix applied
lib/evas/common/evas_cpu.c: In function ‘evas_common_cpu_init’: lib/evas/common/evas_cpu.c:282:11: warning: implicit declaration of function ‘evas_common_cpu_feature_test’; did you mean ‘evas_common_cpu_sve_test’? [-Wimplicit-function-declaration] evas_common_cpu_feature_test(evas_common_cpu_sve_test); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ evas_common_cpu_sve_test
the neon disable on aarch64 comes from https://src.fedoraproject.org/rpms/efl/c/3d251e21067c89d8614a7b818cfb6370f5f72bde?branch=master - seems our guys were wrong
aha, yes, I did with --disable-neon, it's inherited option from from our 32-bit arm build
Let me check, if it's not an issue with the CI setup that builds EFL daily.
I'm building on APM Mustang X-Gene
Tue, Dec 4
Sep 15 2017
Sep 5 2017
Sep 4 2017
Hi, the commit doesn't seem to be correct, the "for" cycle uses the "last" variable, but it's available only when efl is built with valgrind (guarded by #ifndef NVALGRIND).
first there is a warning in the build