All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 904] [dpdk-19.11.11] Meson build has some failures on Fedora35 with clang 13.0.0
Date: Mon, 13 Dec 2021 09:08:28 +0000	[thread overview]
Message-ID: <bug-904-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=904

            Bug ID: 904
           Summary: [dpdk-19.11.11] Meson build has some failures on
                    Fedora35 with clang 13.0.0
           Product: DPDK
           Version: 19.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: meson
          Assignee: dev@dpdk.org
          Reporter: longfengx.liang@intel.com
  Target Milestone: ---

1.DPDK version:
commit 928100dd6d30e733be411380fdb78c68a061936c (HEAD, tag: v19.11.11-rc1,
origin/19.11)
Author: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Date:   Thu Dec 9 15:33:57 2021 +0100

    version: 19.11.11-rc1

    Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>

2.OS version:
  OS: Fedora35 /5.14.17-301.fc35.x86_64
    gcc version: gcc (GCC) 11.2.1 20210728 (Red Hat 11.2.1-1)
    clang version: clang version 13.0.0 (Fedora 13.0.0~rc1-1.fc35)
    ninja version: 1.10.2.git.kitware.jobserver-1
    meson version: 0.60.1

3.build cmd:
CC=clang meson setup build-clang && ninja -C build-clang

4.Error info:

Found ninja-1.10.2.git.kitware.jobserver-1 at /usr/local/bin/ninja
Cleaning... 4 files.
[47/1915] Compiling C object lib/librte_eal.a.p/librte_eal_linux_eal_eal.c.o
../lib/librte_eal/linux/eal/eal.c:590:11: warning: variable 'total_mem' set but
not used [-Wunused-but-set-variable]
        uint64_t total_mem = 0;
                 ^
1 warning generated.
[208/1915] Compiling C object
lib/librte_power.a.p/librte_power_rte_power_empty_poll.c.o
../lib/librte_power/rte_power_empty_poll.c:210:25: warning: variable 'tot_ppi'
set but not used [-Wunused-but-set-variable]
        uint64_t tot_edpi = 0, tot_ppi = 0;
                               ^
1 warning generated.
[444/1915] Compiling C object
drivers/libtmp_rte_bus_fslmc.a.p/bus_fslmc_fslmc_bus.c.o
../drivers/bus/fslmc/fslmc_bus.c:311:6: warning: variable 'device_count' set
but not used [-Wunused-but-set-variable]
        int device_count = 0;
            ^
1 warning generated.
[870/1915] Compiling C object
drivers/net/hinic/base/libhinic_base.a.p/hinic_pmd_mgmt.c.o
../drivers/net/hinic/base/hinic_pmd_mgmt.c:136:6: warning: variable
'cmd_buf_max' set but not used [-Wunused-but-set-variable]
        u32 cmd_buf_max = MAX_PF_MGMT_BUF_SIZE;
            ^
../drivers/net/hinic/base/hinic_pmd_mgmt.c:613:6: warning: variable
'msg_buf_max' set but not used [-Wunused-but-set-variable]
        u32 msg_buf_max = MAX_PF_MGMT_BUF_SIZE;
            ^
2 warnings generated.
[894/1915] Compiling C object app/test/dpdk-test.p/test_cmdline_ipaddr.c.o
../app/test/test_cmdline_ipaddr.c:259:3: warning: suspicious concatenation of
string literals in an array initialization; did you mean to separate the
elements with a comma? [-Wstring-concatenation]
                "random invalid text",
                ^
../app/test/test_cmdline_ipaddr.c:258:3: note: place parentheses around the
string literal to silence warning
                "1234:1234:1234:1234:1234:1234:1234:1234:1234:1234:1234"
                ^
1 warning generated.
[902/1915] Compiling C object app/test/dpdk-test.p/test_cmdline_num.c.o
../app/test/test_cmdline_num.c:204:5: warning: suspicious concatenation of
string literals in an array initialization; did you mean to separate the
elements with a comma? [-Wstring-concatenation]
                 
"1111000011110000111100001111000011110000111100001111000011110000",
                  ^
../app/test/test_cmdline_num.c:203:3: note: place parentheses around the string
literal to silence warning
               
"0b1111000011110000111100001111000011110000111100001111000011110000"
                ^
1 warning generated.
[958/1915] Compiling C object
drivers/libtmp_rte_pmd_ifc.a.p/net_ifc_ifcvf_vdpa.c.o
In file included from ../drivers/net/ifc/ifcvf_vdpa.c:25:
../drivers/net/ifc/base/ifcvf.h:16:9: warning: 'VIRTIO_F_IOMMU_PLATFORM' macro
redefined [-Wmacro-redefined]
#define VIRTIO_F_IOMMU_PLATFORM         33
        ^
/usr/include/linux/virtio_config.h:78:9: note: previous definition is here
#define VIRTIO_F_IOMMU_PLATFORM         VIRTIO_F_ACCESS_PLATFORM
        ^
1 warning generated.
[1026/1915] Compiling C object
drivers/libtmp_rte_pmd_liquidio.a.p/net_liquidio_lio_rxtx.c.o
../drivers/net/liquidio/lio_rxtx.c:1053:11: warning: variable
'tot_inst_processed' set but not used [-Wunused-but-set-variable]
        uint32_t tot_inst_processed = 0;
                 ^
1 warning generated.
[1084/1915] Compiling C object
drivers/libtmp_rte_pmd_nfp.a.p/net_nfp_nfp_net.c.o
../drivers/net/nfp/nfp_net.c:2597:11: warning: variable 'rss_hf' set but not
used [-Wunused-but-set-variable]
        uint64_t rss_hf;
                 ^
../drivers/net/nfp/nfp_net.c:3014:24: warning: variable 'totlen' set but not
used [-Wunused-but-set-variable]
        size_t count, curlen, totlen = 0;
                              ^
../drivers/net/nfp/nfp_net.c:3116:24: warning: variable 'totlen' set but not
used [-Wunused-but-set-variable]
        size_t count, curlen, totlen = 0;
                              ^
3 warnings generated.
[1158/1915] Compiling C object
drivers/net/qede/base/libqede_base.a.p/ecore_vf.c.o
../drivers/net/qede/base/ecore_vf.c:76:19: warning: parameter 'resp_size' set
but not used [-Wunused-but-set-parameter]
                  u8 *done, u32 resp_size)
                                ^
1 warning generated.
[1343/1915] Compiling C object
drivers/libtmp_rte_pmd_vmxnet3.a.p/net_vmxnet3_vmxnet3_rxtx.c.o
../drivers/net/vmxnet3/vmxnet3_rxtx.c:330:6: warning: variable 'completed' set
but not used [-Wunused-but-set-variable]
        int completed = 0;
            ^
1 warning generated.
[1440/1915] Linking target drivers/librte_pmd_aesni_gcm.so.20.0
FAILED: drivers/librte_pmd_aesni_gcm.so.20.0
clang  -o drivers/librte_pmd_aesni_gcm.so.20.0
drivers/librte_pmd_aesni_gcm.so.20.0.p/meson-generated_.._rte_pmd_aesni_gcm.pmd.c.o
drivers/libtmp_rte_pmd_aesni_gcm.a.p/crypto_aesni_gcm_aesni_gcm_pmd.c.o
drivers/libtmp_rte_pmd_aesni_gcm.a.p/crypto_aesni_gcm_aesni_gcm_pmd_ops.c.o
-Wl,--as-needed -Wl,--no-undefined -Wl,-O1 -shared -fPIC -Wl,--start-group
-Wl,-soname,librte_pmd_aesni_gcm.so.20.0 -Wl,--no-as-needed -pthread -lm -ldl
-lnuma '-Wl,-rpath,$ORIGIN/../lib:$ORIGIN/'
-Wl,-rpath-link,/root/19.11.11-lts/build-clang/lib
-Wl,-rpath-link,/root/19.11.11-lts/build-clang/drivers
lib/librte_cryptodev.so.20.0 lib/librte_eal.so.20.0 lib/librte_kvargs.so.20.0
lib/librte_mbuf.so.20.0 lib/librte_mempool.so.20.0 lib/librte_ring.so.20.0
drivers/librte_bus_vdev.so.20.0
-Wl,--version-script=/root/19.11.11-lts/drivers/crypto/aesni_gcm/rte_pmd_aesni_gcm_version.map
-lIPSec_MB -Wl,--end-group
/usr/bin/ld:
drivers/libtmp_rte_pmd_aesni_gcm.a.p/crypto_aesni_gcm_aesni_gcm_pmd_ops.c.o:(.bss+0x0):
multiple definition of `aesni_gcm_logtype_driver';
drivers/libtmp_rte_pmd_aesni_gcm.a.p/crypto_aesni_gcm_aesni_gcm_pmd.c.o:(.bss+0x0):
first defined here
clang-13: error: linker command failed with exit code 1 (use -v to see
invocation)
[1449/1915] Compiling C object
drivers/libtmp_rte_pmd_dpaa_sec.a.p/crypto_dpaa_sec_dpaa_sec.c.o
ninja: build stopped: subcommand failed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2021-12-13  9:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13  9:08 bugzilla [this message]
2022-01-04 14:20 ` [Bug 904] [dpdk-19.11.11] Meson build has some failures on Fedora35 with clang 13.0.0 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-904-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.