DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 837] [build]lib/ethdev build failed on Ubuntu20.04.3 with gcc 10.3.0.
Date: Tue, 26 Oct 2021 08:11:01 +0000	[thread overview]
Message-ID: <bug-837-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 837
           Summary: [build]lib/ethdev build failed on Ubuntu20.04.3 with
                    gcc 10.3.0.
           Product: DPDK
           Version: 21.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: meson
          Assignee: dev@dpdk.org
          Reporter: longfengx.liang@intel.com
  Target Milestone: ---

1.DPDK version:
Now build failed issue branch dpdk-next-net/dpdk-next-net-intel
bad commit d7a55a39bce30d3bf7e9e7de3f25b1f603b63926 (HEAD -> main)
Author: Ferruh Yigit <ferruh.yigit@intel.com>
Date:   Fri Oct 22 12:03:12 2021 +0100

    ethdev: add namespace

    Add 'RTE_ETH' namespace to all enums & macros in a backward compatible
    way. The macros for backward compatibility can be removed in next LTS.
    Also updated some struct names to have 'rte_eth' prefix.

    All internal components switched to using new names.

    Syntax fixed on lines that this patch touches.

    Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
    Acked-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
    Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
    Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
    Acked-by: Jerin Jacob <jerinj@marvell.com>
    Acked-by: Wisam Jaddo <wisamm@nvidia.com>
    Acked-by: Rosen Xu <rosen.xu@intel.com>
    Acked-by: Chenbo Xia <chenbo.xia@intel.com>
    Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
    Acked-by: Somnath Kotur <somnath.kotur@broadcom.com>


2.OS version:
  Ubuntu 20.04.3 LTS /kernel 5.8.0-48-generic
  gcc version:gcc (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0

3.Test Setup:

build cmd:
CC=gcc meson --werror -Denable_kmods=True -Dlibdir=lib -Denable_docs=true
x86_64-native-linuxapp-doc
ninja -C x86_64-native-linuxapp-doc/


4.build failed output info:
root@dpdk-xuemin4x-ub2004-doc:~/dpdk-next-net# ninja -C
x86_64-native-linuxapp-doc/
ninja: Entering directory `x86_64-native-linuxapp-doc/'
[2668/2697] Generating rte_kni with a custom command.
make: Entering directory '/usr/src/linux-headers-5.8.0-48-generic'
  CC [M] 
/root/dpdk-next-net/x86_64-native-linuxapp-doc/kernel/linux/kni/kni_net.o
  CC [M] 
/root/dpdk-next-net/x86_64-native-linuxapp-doc/kernel/linux/kni/kni_misc.o
  LD [M] 
/root/dpdk-next-net/x86_64-native-linuxapp-doc/kernel/linux/kni/rte_kni.o
  MODPOST
/root/dpdk-next-net/x86_64-native-linuxapp-doc/kernel/linux/kni/Module.symvers
  CC [M] 
/root/dpdk-next-net/x86_64-native-linuxapp-doc/kernel/linux/kni/rte_kni.mod.o
  LD [M] 
/root/dpdk-next-net/x86_64-native-linuxapp-doc/kernel/linux/kni/rte_kni.ko
make: Leaving directory '/usr/src/linux-headers-5.8.0-48-generic'
[2671/2697] Generating doxygen with a custom command.
FAILED: doc/api/html
/root/dpdk-next-net/doc/api/generate_doxygen.sh doc/api/doxy-api.conf
doc/api/html /root/dpdk-next-net/doc/api/doxy-html-custom.sh
/root/dpdk-next-net/lib/ethdev/rte_ethdev.h:397: error: Member
RTE_ETH_MQ_RX_RSS_FLAG (macro definition) of file rte_ethdev.h is not
documented. (warning treated as error, aborting now)
[2676/2697] Compiling C object
'drivers/a715181@@tmp_rte_event_octeontx2@sta/event_octeontx2_otx2_worker_dual.c.o'.
ninja: build stopped: subcommand failed.

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

             reply	other threads:[~2021-10-26  8:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  8:11 bugzilla [this message]
2021-10-26  8: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-837-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).