From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 873] net/iavf build failure in Windows with clang
Date: Mon, 01 Nov 2021 09:56:32 +0000 [thread overview]
Message-ID: <bug-873-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=873
Bug ID: 873
Summary: net/iavf build failure in Windows with clang
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: alialnu@nvidia.com
Target Milestone: ---
"""
$ meson.exe --werror build
$ ninja.exe -C build
[..]
[184/600] Compiling C object
drivers/a715181@@tmp_rte_net_i40e@sta/net_i40e_rte_pmd_i40e.c.obj
[185/600] Compiling C object
drivers/a715181@@tmp_rte_net_i40e@sta/net_i40e_i40e_rxtx_vec_sse.c.obj
[186/600] Compiling C object
drivers/a715181@@tmp_rte_net_iavf@sta/net_iavf_iavf_ipsec_crypto.c.obj
FAILED: drivers/a715181@@tmp_rte_net_iavf@sta/net_iavf_iavf_ipsec_crypto.c.obj
clang
@drivers/a715181@@tmp_rte_net_iavf@sta/net_iavf_iavf_ipsec_crypto.c.obj.rsp
../drivers/net/iavf/iavf_ipsec_crypto.c:112:32: error: comparison of integers
of different signs: 'const enum rte_crypto_cipher_algorithm' and 'uint32_t'
(aka 'unsigned int') [-Werror,-Wsign-compare]
capability->sym.cipher.algo == algo)
~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~~~~
../drivers/net/iavf/iavf_ipsec_crypto.c:111:31: error: comparison of integers
of different signs: 'const enum rte_crypto_sym_xform_type' and 'uint32_t' (aka
'unsigned int') [-Werror,-Wsign-compare]
capability->sym.xform_type == type &&
~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~~~~
2 errors generated.
"""
Meson: 0.54.3
Ninja: 1.10.2
Clang: 11.0.0
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-11-01 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 9:56 bugzilla [this message]
2021-11-01 13:29 ` bugzilla
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=bug-873-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/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).