en Copyright 2015 Java http://172.16.0.5:8080/history/dpdk/config/x86/#ab5ac1ad config/x86: fix MinGW cross build with Meson 0.49Cross build with MinGW was broken for the baseline meson 0.49.2.Cause: in c_args = '-mno-avx512f' from config/x86/cross-mingw,each character was treated as a separate compiler option: meson.build:4:0: ERROR: Compiler x86_64-w64-mingw32-gcc can not compile programs.With c_args = ['-mno-avx512f'] configuration passed, but build failed,because Meson placed -mno-avx512f after -mavx512f in CFLAGS: In file included from /usr/lib/gcc/x86_64-w64-mingw32/9.3-win32/include/immintrin.h:55, from /usr/lib/gcc/x86_64-w64-mingw32/9.3-win32/include/x86intrin.h:32, from ../dpdk/lib/net/net_crc_avx512.c:13: /usr/lib/gcc/x86_64-w64-mingw32/9.3-win32/include/avx512fintrin.h:1650:1: error: inlining failed in call to always_inline _mm512_ternarylogic_epi64: target specific option mismatch 1650 | _mm512_ternarylogic_epi64 (__m512i __A, __m512i __B, __m512i __C, | ^~~~~~~~~~~~~~~~~~~~~~~~~ ../dpdk/lib/net/net_crc_avx512.c:59:9: note: called from here 59 | return _mm512_ternarylogic_epi64(tmp0, tmp1, data_block, 0x96); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Additionally, -m[no-]avx512f flag is expected to be in machine_argsby all the checks in meson.build files.Commit 419c6e9af69e ("net/i40e: fix build for Windows MinGW")fixed the errors cause by MinGW using AVX512F on Windows.The binutils AVX512F bug check is now portable,so enable it for Windows to switch AVX512 support on and offwithout any special logic for MinGW.Fixes: 549bfc83168f ("config: disable AVX512 with MinGW")Signed-off-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>Acked-by: Bruce Richardson <bruce.richardson@intel.com> List of files: /dpdk/config/x86/cross-mingw Fri, 12 Nov 2021 21:00:00 +0000 Dmitry Kozlyuk <dmitry.kozliuk@gmail.com> http://172.16.0.5:8080/history/dpdk/config/x86/#ecb904cc build: fix warnings when running external commandsMeson 0.61.1 is giving warnings that the calls to run_command do notalways explicitly specify if the result is to be checked or not, i.e.there is a missing "check" parameter. This is because the defaultbehaviour without the parameter is due to change in the future.We can fix these warnings by explicitly adding into each call whetherthe result should be checked by meson or not. This patch thereforeadds in "check: false" to each run_command call where the result isbeing checked by the DPDK meson.build code afterwards, and adds in"check: true" to any calls where the result is currently unchecked.Bugzilla ID: 921Cc: stable@dpdk.orgReported-by: Jerin Jacob <jerinj@marvell.com>Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>Tested-by: Jerin Jacob <jerinj@marvell.com> List of files: /dpdk/config/x86/meson.build Thu, 20 Jan 2022 18:00:00 +0000 Bruce Richardson <bruce.richardson@intel.com>