From: David Marchand <david.marchand@redhat.com>
To: Brandon Lo <blo@iol.unh.edu>, Xiao Wang <xiao.w.wang@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: ci@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
dpdklab@iol.unh.edu
Subject: Re: [dpdk-ci] Fedora Rawhide Meson Compile Testing - DPDK Compile Warning
Date: Fri, 2 Oct 2020 08:51:05 +0200 [thread overview]
Message-ID: <CAJFAV8yAeuCG68y5HKN5QLUZOs+8A2d_+hA__WY=M1bzoBe32w@mail.gmail.com> (raw)
In-Reply-To: <CAOeXdvatG8S20KgQuRaqGG_6aDNLGrgzg1W=f0Ps2c4BRFWUxg@mail.gmail.com>
On Thu, Oct 1, 2020 at 8:24 PM Brandon Lo <blo@iol.unh.edu> wrote:
> We have successfully added Fedora Rawhide to our production pipeline
> for Meson compile testing.
> The image for the container will be updated on a weekly basis.
>
> The version of GCC that it is currently running (10.2) catches that
> the drivers/vdpa/ifc/base/ifcvf.h file redefines
> VIRTIO_F_IOMMU_PLATFORM, originally from
> /usr/include/linux/virtio_config.h.
> I am just giving you guys a heads-up before the failure report catches
> anyone off guard.
Brandon,
Before putting this new job online, the build issue should have been
fixed on the dpdk side.
All new submitted series are now getting a fail flag that we must
inspect to check whether it is because of this known issue or
something else.
Please, disable this job.
There is also the OpenSuse job failing.
Can you investigate?
Xiao, Maxime,
Anyone free to have a look on the vdpa build issue on Fedora Rawhide?
FAILED: drivers/libtmp_rte_pmd_ifc.a.p/vdpa_ifc_ifcvf_vdpa.c.o
cc -Idrivers/libtmp_rte_pmd_ifc.a.p -Idrivers -I../drivers
-Idrivers/vdpa/ifc -I../drivers/vdpa/ifc -I../drivers/vdpa/ifc/base
-Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -I.
-I.. -Iconfig -I../config -Ilib/librte_eal/include
-I../lib/librte_eal/include -Ilib/librte_eal/linux/include
-I../lib/librte_eal/linux/include -Ilib/librte_eal/x86/include
-I../lib/librte_eal/x86/include -Ilib/librte_eal/common
-I../lib/librte_eal/common -Ilib/librte_eal -I../lib/librte_eal
-Ilib/librte_kvargs -I../lib/librte_kvargs -Ilib/librte_metrics
-I../lib/librte_metrics -Ilib/librte_telemetry
-I../lib/librte_telemetry -Ilib/librte_pci -I../lib/librte_pci
-Ilib/librte_vhost -I../lib/librte_vhost -Ilib/librte_ethdev
-I../lib/librte_ethdev -Ilib/librte_net -I../lib/librte_net
-Ilib/librte_mbuf -I../lib/librte_mbuf -Ilib/librte_mempool
-I../lib/librte_mempool -Ilib/librte_ring -I../lib/librte_ring
-Ilib/librte_meter -I../lib/librte_meter -Ilib/librte_cryptodev
-I../lib/librte_cryptodev -Ilib/librte_hash -I../lib/librte_hash
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall
-Winvalid-pch -Werror -O3 -include rte_config.h -Wextra -Wcast-qual
-Wdeprecated -Wformat-nonliteral -Wformat-security
-Wmissing-declarations -Wmissing-prototypes -Wnested-externs
-Wold-style-definition -Wpointer-arith -Wsign-compare
-Wstrict-prototypes -Wundef -Wwrite-strings
-Wno-address-of-packed-member -Wno-packed-not-aligned
-Wno-missing-field-initializers -Wno-zero-length-bounds -D_GNU_SOURCE
-fPIC -march=native -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API
-Wno-format-truncation -MD -MQ
drivers/libtmp_rte_pmd_ifc.a.p/vdpa_ifc_ifcvf_vdpa.c.o -MF
drivers/libtmp_rte_pmd_ifc.a.p/vdpa_ifc_ifcvf_vdpa.c.o.d -o
drivers/libtmp_rte_pmd_ifc.a.p/vdpa_ifc_ifcvf_vdpa.c.o -c
../drivers/vdpa/ifc/ifcvf_vdpa.c
In file included from ../drivers/vdpa/ifc/ifcvf_vdpa.c:26:
../drivers/vdpa/ifc/base/ifcvf.h:16: error: "VIRTIO_F_IOMMU_PLATFORM"
redefined [-Werror]
16 | #define VIRTIO_F_IOMMU_PLATFORM 33
|
In file included from /usr/include/linux/virtio_net.h:30,
from ../drivers/vdpa/ifc/ifcvf_vdpa.c:11:
/usr/include/linux/virtio_config.h:78: note: this is the location of
the previous definition
78 | #define VIRTIO_F_IOMMU_PLATFORM VIRTIO_F_ACCESS_PLATFORM
|
cc1: all warnings being treated as errors
Thanks guys.
--
David Marchand
next prev parent reply other threads:[~2020-10-02 6:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 18:23 Brandon Lo
2020-10-02 6:51 ` David Marchand [this message]
2020-10-02 16:44 ` David Marchand
2020-10-06 9:50 ` David Marchand
2020-10-06 12:52 ` [dpdk-ci] [dpdklab] " Lincoln Lavoie
2020-10-06 13:03 ` Thomas Monjalon
2020-10-06 13:22 ` Lincoln Lavoie
2020-10-06 13:30 ` Thomas Monjalon
2020-10-06 14:07 ` Brandon Lo
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='CAJFAV8yAeuCG68y5HKN5QLUZOs+8A2d_+hA__WY=M1bzoBe32w@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=blo@iol.unh.edu \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=maxime.coquelin@redhat.com \
--cc=thomas@monjalon.net \
--cc=xiao.w.wang@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).