From: Ali Alnubani <alialnu@nvidia.com>
To: Haiyue Wang <haiyue.wang@intel.com>, "stable@dpdk.org" <stable@dpdk.org>
Cc: "christian.ehrhardt@canonical.com"
<christian.ehrhardt@canonical.com>,
"yux.jiang@intel.com" <yux.jiang@intel.com>,
"qi.z.zhang@intel.com" <qi.z.zhang@intel.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: RE: [PATCH 19.11 v1 1/3] net/ixgbe: build failure with make and clang 13
Date: Tue, 14 Dec 2021 17:23:02 +0000 [thread overview]
Message-ID: <DM4PR12MB516746DBC1619B7D042A671DDA759@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20211214162935.368215-1-haiyue.wang@intel.com>
> -----Original Message-----
> From: Haiyue Wang <haiyue.wang@intel.com>
> Sent: Tuesday, December 14, 2021 6:30 PM
> To: stable@dpdk.org
> Cc: christian.ehrhardt@canonical.com; yux.jiang@intel.com;
> qi.z.zhang@intel.com; Haiyue Wang <haiyue.wang@intel.com>; Wenzhuo Lu
> <wenzhuo.lu@intel.com>; Konstantin Ananyev
> <konstantin.ananyev@intel.com>
> Subject: [PATCH 19.11 v1 1/3] net/ixgbe: build failure with make and clang 13
>
> Disable the -Wunused-but-set-variable option for clang to avoid
> compile warning.
>
> Bugzilla ID: 900
Do you mean "Bugzilla ID: 903"?
https://bugs.dpdk.org/show_bug.cgi?id=900 is a net/nfp build failure.
>
> Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
> ---
> drivers/net/ixgbe/Makefile | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/ixgbe/Makefile b/drivers/net/ixgbe/Makefile
> index 31523025b3..31a418a2c6 100644
> --- a/drivers/net/ixgbe/Makefile
> +++ b/drivers/net/ixgbe/Makefile
> @@ -29,6 +29,7 @@ else ifeq ($(CONFIG_RTE_TOOLCHAIN_CLANG),y)
> #
> CFLAGS_BASE_DRIVER = -Wno-unused-parameter -Wno-unused-value
> CFLAGS_BASE_DRIVER += -Wno-strict-aliasing -Wno-format-extra-args
> +CFLAGS_BASE_DRIVER += -Wno-unused-but-set-variable
>
> else
> #
> --
> 2.34.1
Thanks Haiyue for looking into this.
I no longer see the build failures in Bugzilla tickets 901/902/903, but I now see similar build errors in net/qede and net/sfc.
next prev parent reply other threads:[~2021-12-14 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 16:29 Haiyue Wang
2021-12-14 16:29 ` [PATCH 19.11 v1 2/3] net/i40e: " Haiyue Wang
2021-12-15 13:40 ` Christian Ehrhardt
2021-12-14 16:29 ` [PATCH 19.11 v1 3/3] net/ice: " Haiyue Wang
2021-12-14 17:23 ` Ali Alnubani [this message]
2021-12-15 1:05 ` [PATCH 19.11 v1 1/3] net/ixgbe: " Wang, Haiyue
2021-12-20 10:48 [PATCH 19.11 v1 1/3] net/ixgbe: build failure with make and clang < 13 Haiyue Wang
2022-01-03 11:34 ` Christian Ehrhardt
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=DM4PR12MB516746DBC1619B7D042A671DDA759@DM4PR12MB5167.namprd12.prod.outlook.com \
--to=alialnu@nvidia.com \
--cc=christian.ehrhardt@canonical.com \
--cc=haiyue.wang@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=wenzhuo.lu@intel.com \
--cc=yux.jiang@intel.com \
/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).