DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, <dev@dpdk.org>
Cc: <bruce.richardson@intel.com>, <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/5] more build tests
Date: Wed, 15 Sep 2021 21:27:01 +0100	[thread overview]
Message-ID: <b1d0c60e-be70-9414-5686-752af3a84b45@intel.com> (raw)
In-Reply-To: <20210808125139.3573701-1-thomas@monjalon.net>

On 8/8/2021 1:51 PM, Thomas Monjalon wrote:
> While testing more build types, some errors occur.
> 
> v3: fix minsize build with GCC
> v2: fix init of var buildtype
> 
> Thomas Monjalon (5):
>   net/qede: fix minsize build
>   regex/mlx5: fix minsize build
>   vdpa/mlx5: fix minsize build
>   test/crypto: fix minsize build
>   devtools: test different build types
> 
>  app/test/test_cryptodev_blockcipher.c    |  2 +-
>  devtools/test-meson-builds.sh            | 19 +++++++++++++------
>  drivers/net/qede/qede_rxtx.c             |  3 ++-
>  drivers/regex/mlx5/mlx5_regex_fastpath.c |  3 ++-
>  drivers/vdpa/mlx5/mlx5_vdpa_mem.c        |  4 ++--
>  5 files changed, 20 insertions(+), 11 deletions(-)
> 

With the 'test-meson-builds.sh' update (patch 5/5) clang crashes for me [1], it
can be related to my environment but I can reproduce the issue 100%.


When the patch 5/5 is dropped, I confirm it builds fine with
'--buildtype=minsize' meson option.

So _only for first four patches_:
Tested-by: Ferruh Yigit <ferruh.yigit@intel.com>


[1]
FAILED: drivers/libtmp_rte_crypto_ccp.a.p/crypto_ccp_ccp_dev.c.o
clang-12: error: clang frontend command failed with exit code 70 (use -v to see
invocation)

  parent reply	other threads:[~2021-09-15 20:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 21:53 [dpdk-dev] [PATCH] devtools: test different build types Thomas Monjalon
2021-05-21 15:03 ` David Marchand
2021-07-23 20:26   ` Andrew Rybchenko
2021-08-02 22:45 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2021-08-08 12:51 ` [dpdk-dev] [PATCH v3 0/5] more build tests Thomas Monjalon
2021-08-08 12:51   ` [dpdk-dev] [PATCH v3 1/5] net/qede: fix minsize build Thomas Monjalon
2021-08-09  5:15     ` [dpdk-dev] [EXT] " Devendra Singh Rawat
2021-08-09  7:11       ` Rasesh Mody
2021-09-15 15:16       ` David Marchand
2021-08-08 12:51   ` [dpdk-dev] [PATCH v3 2/5] regex/mlx5: " Thomas Monjalon
2021-08-11  8:48     ` Ruifeng Wang
2021-08-08 12:51   ` [dpdk-dev] [PATCH v3 3/5] vdpa/mlx5: " Thomas Monjalon
2021-08-09  6:43     ` Matan Azrad
2021-08-11  8:48     ` Ruifeng Wang
2021-08-08 12:51   ` [dpdk-dev] [PATCH v3 4/5] test/crypto: " Thomas Monjalon
2021-08-11  8:48     ` Ruifeng Wang
2021-08-08 12:51   ` [dpdk-dev] [PATCH v3 5/5] devtools: test different build types Thomas Monjalon
2024-08-15 16:26     ` Stephen Hemminger
2021-09-15 20:27   ` Ferruh Yigit [this message]
2021-09-16  7:05   ` [dpdk-dev] [PATCH v3 0/5] more build tests David Marchand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b1d0c60e-be70-9414-5686-752af3a84b45@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).