From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 378BEA00C4; Fri, 7 Oct 2022 15:18:14 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D9126400D5; Fri, 7 Oct 2022 15:18:13 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id E1A3240042 for ; Fri, 7 Oct 2022 15:18:11 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1665148691; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=oUDRaDsqVos4T3q/Vv2wgmzqHszmZhXCsTB7oWo/R+A=; b=X1gC6a60u8fTak+JwjcPJXxU73M4mFZvlJ5mH6mSYhNqEg12eHudY2QCB/tL/cryhdL2Tp 5aM5Dw2O9ZRT4fwa4paNzviqjRreIBzm970Gz3wikVfzeSxpFq3ZrtPtUOdGcBh0zwrenI ZKEYaflxeQ+rMHxw6LhGDoe2vN1ntK0= Received: from mail-pl1-f199.google.com (mail-pl1-f199.google.com [209.85.214.199]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-135-wf7iRmJxPtKc6zT3pTHGtw-1; Fri, 07 Oct 2022 09:18:10 -0400 X-MC-Unique: wf7iRmJxPtKc6zT3pTHGtw-1 Received: by mail-pl1-f199.google.com with SMTP id m10-20020a170902db0a00b001789bd49db9so3385002plx.23 for ; Fri, 07 Oct 2022 06:18:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=oUDRaDsqVos4T3q/Vv2wgmzqHszmZhXCsTB7oWo/R+A=; b=bzZou1IBsMD3Eb2fyG5MwPrI/C4u9n98puEDUJvMVJICflVE/OI2CKWgeA+rDYRkH6 eOEuds9J08M7rRRIs1kXb0kh35TcsrVuCzme5QgFdhC1wu1Tld2yDMw4GbAlRzY/Tf4x 3H45GqbC+9IP6AKC2+kXAqA3E/HyuFtNU0XfVFiKk2xRKui9CxVuYns7mseJgytOP63v e0tuRfc0k+kz4W2R9DPJtt34K/kJWFjPP14SYoxWqZmSv6vxm5tBBl3j4XDthVCGOPNO feiILfPD/rtXN6QrSg5bpyA3yBKmXhujhKviGhGmVZIWNKO9M3DSK1UauT9+AmuVO3pD wf4w== X-Gm-Message-State: ACrzQf35j4UAK2DfKUz8IncL57Ovzzlt5naOVUnIV4fCsV5oOo1fQ1/p pXCqTPDvTBKesJGN9D5bB2NcHE716CCkMXv254iJXrxru2YGpuH0SsUly7OWzYj1HagYPHfeoUQ 7dcf2jUm1MMKe5byWMkE= X-Received: by 2002:a63:5b58:0:b0:452:2ba4:f86b with SMTP id l24-20020a635b58000000b004522ba4f86bmr4383697pgm.223.1665148689212; Fri, 07 Oct 2022 06:18:09 -0700 (PDT) X-Google-Smtp-Source: AMsMyM72jGudPUrSuNvlec3jcgvJrcHyYaXQFKL3+5FrUXVIoapyWVcJaZIWPpC6fIN1BzG0d7+t8dh6oZuGem/imTM= X-Received: by 2002:a63:5b58:0:b0:452:2ba4:f86b with SMTP id l24-20020a635b58000000b004522ba4f86bmr4383672pgm.223.1665148688904; Fri, 07 Oct 2022 06:18:08 -0700 (PDT) MIME-Version: 1.0 References: <20220912170747.3128065-1-bruce.richardson@intel.com> <20220912170747.3128065-2-bruce.richardson@intel.com> In-Reply-To: <20220912170747.3128065-2-bruce.richardson@intel.com> From: David Marchand Date: Fri, 7 Oct 2022 15:17:57 +0200 Message-ID: Subject: Re: [PATCH 1/1] build: increase minimum meson version to 0.53 To: Bruce Richardson , Thomas Monjalon Cc: dev@dpdk.org, Lincoln Lavoie , techboard@dpdk.org X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Mon, Sep 12, 2022 at 7:08 PM Bruce Richardson wrote: > > This patchset bumps the minimum meson version from 0.49.2 to 0.53. > Rather than specifying a specific point-release of 0.53, as was done > with 0.49, the version specifier is kept to the major release number > only for simplicity, as new features are not introduces into bugfix > releases of meson. > > Some new features of interest which can now be used in DPDK with this > new minimum meson version: > > * can do header-file checks directly inside find_library calls, rather > than needing a separate check.[v0.50]. > * can pass multiple cross-files at the same time when cross-compiling > [v0.51]. > * "alias_target" function, to allow use to give better/shorter names > for particular build objects [v0.52]. > * auto-generation of clang-format [v0.50] and clang-tidy[v0.52] targets > when those tools are present and config dotfiles are present. > Similarly ctags and cscope are added as targets when those tools are > present [v0.53] > * meson module for filesystem operations, so meson can now check for the > presence of particlar files or directories [v0.53]. > * "summary" function to provide a configuration summary at the end of > the meson run [v0.53]. > > Plus many other features. See [1] for full details of each version. > > [1] https://mesonbuild.com/Release-notes.html > > Signed-off-by: Bruce Richardson - We have an issue with mingw cross compilation. https://github.com/ovsrobot/dpdk/actions/runs/3039251235/jobs/4893964186 + meson build --werror --cross-file config/x86/cross-mingw -Dexamples=helloworld -Dplatform=generic --default-library=static --buildtype=debugoptimized -Dcheck_includes=true The Meson build system Version: 0.53.0 Source dir: /home/runner/work/dpdk/dpdk Build dir: /home/runner/work/dpdk/dpdk/build Build type: cross build Program cat found: YES (/usr/bin/cat) Project name: DPDK Project version: 22.11.0-rc0 C compiler for the build machine: ccache gcc (gcc 9.4.0 "gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0") C linker for the build machine: gcc GNU ld.bfd 2.34 meson.build:4:0: ERROR: Unable to determine dynamic linker - I reproduced locally, it looks like meson is trying to pass some -fuse-ld option that is not understood. 4577 write(2, "x86_64-w64-mingw32-gcc: error: unrecognized command line option \342\200\230-fuse-ld=x86_64-w64-mingw32-ld\342\200\231\n", 101) = 101 - Upgrading to 0.53.1, I don't see the issue anymore for mingw, so I pushed a branch in GHA to get a status for other targets. https://github.com/david-marchand/dpdk/actions/runs/3205007946 -- David Marchand