From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1022] [dpdk 22.07-rc0] meson build failed with doc args on Ubuntu22.04 with gcc11.2.0
Date: Wed, 01 Jun 2022 05:36:43 +0000 [thread overview]
Message-ID: <bug-1022-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1022
Bug ID: 1022
Summary: [dpdk 22.07-rc0] meson build failed with doc args on
Ubuntu22.04 with gcc11.2.0
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: daxuex.gao@intel.com
Target Milestone: ---
[DPDK Version]
commit f62212d39a1b5f1118dabbdfcbae1ac6394291a7 (HEAD, origin/main,
origin/HEAD, main)
Author: Huichao Cai <chcchc88@163.com>
Date: Fri Apr 15 11:26:50 2022 +0800
ip_frag: add IPv4 options fragment
According to RFC791,the options may appear or not in datagrams.
They must be implemented by all IP modules (host and gateways).
What is optional is their transmission in any particular datagram,
not their implementation. So we have to deal with it during the
fragmenting process.
Add some test data for the IPv4 header optional field fragmenting.
Signed-off-by: Huichao Cai <chcchc88@163.com>
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
[OS version]
Ubuntu22.04 LTS/(5.17.5-051705-generic/5.15.0-25-generic)
GCC 11.2.0
[Test Setup]
# CC=gcc meson --werror -Denable_kmods=True -Dlibdir=lib -Denable_docs=true
x86-gcc-doc
# ninja -C x86-gcc-doc
[log]
[3413/3417] Generating kernel/linux/kni/rte_kni with a custom command
make: Entering directory '/usr/src/linux-headers-5.15.0-25-generic'
CC [M] /tmp/dpdk/x86-gcc-doc/kernel/linux/kni/kni_misc.o
CC [M] /tmp/dpdk/x86-gcc-doc/kernel/linux/kni/kni_net.o
LD [M] /tmp/dpdk/x86-gcc-doc/kernel/linux/kni/rte_kni.o
MODPOST /tmp/dpdk/x86-gcc-doc/kernel/linux/kni/Module.symvers
CC [M] /tmp/dpdk/x86-gcc-doc/kernel/linux/kni/rte_kni.mod.o
LD [M] /tmp/dpdk/x86-gcc-doc/kernel/linux/kni/rte_kni.ko
BTF [M] /tmp/dpdk/x86-gcc-doc/kernel/linux/kni/rte_kni.ko
Skipping BTF generation for /tmp/dpdk/x86-gcc-doc/kernel/linux/kni/rte_kni.ko
due to unavailability of vmlinux
make: Leaving directory '/usr/src/linux-headers-5.15.0-25-generic'
[3417/3417] Generating doc/guides/html_guides with a custom command
FAILED: doc/guides/html
/usr/bin/python3 ../buildtools/call-sphinx-build.py /usr/bin/sphinx-build
22.07.0-rc0 /tmp/dpdk/doc/guides /tmp/dpdk/x86-gcc-doc/doc/guides -W
Warning, treated as error:
/tmp/dpdk/doc/guides/rel_notes/release_18_05.rst:256:unknown document:
../rawdevs/dpaa2_qdma
ninja: build stopped: subcommand failed.
[Bad commit]
commit 10fa69a71e895f758dd3af52806025d6e78891a1
Author: Nipun Gupta <nipun.gupta@nxp.com>
Date: Thu May 5 14:35:17 2022 +0530
raw/dpaa2_qdma: remove driver
With DMA devices supported as a separate flavor of devices,
the DPAA2 QDMA driver is moved in the DMA devices.
This change removes the DPAA2 QDMA driver from raw devices.
Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com>
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-06-01 5:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 5:36 bugzilla [this message]
2022-06-01 7:16 ` 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-1022-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).