From: Timothy Redaelli <tredaelli@redhat.com>
To: dev@dpdk.org
Cc: stable@dpdk.org
Subject: [dpdk-dev] [PATCH 0/3] examples: fix building with GCC 10
Date: Wed, 5 Feb 2020 14:47:02 +0100 [thread overview]
Message-ID: <cover.1580910264.git.tredaelli@redhat.com> (raw)
GCC 10 defaults to -fno-common, this means a linker error will now be
reported if the same global variable is defined in more than one
compilation unit.
See https://gcc.gnu.org/gcc-10/porting_to.html for more informations.
I didn't put -fcommon to CFLAGS since:
Compiling with -fno-common is useful on targets for which it provides
better performance, or if you wish to verify that the program will work
on other systems that always treat uninitialized variable definitions
this way.
from gcc man page
Timothy Redaelli (3):
examples/vhost_blk: fix building with GCC 10
examples/eventdev_pipeline: fix building with GCC 10
examples/qos_sched: fix building with GCC 10
examples/eventdev_pipeline/main.c | 2 ++
examples/eventdev_pipeline/pipeline_common.h | 4 ++--
examples/qos_sched/cfg_file.c | 3 +++
examples/qos_sched/main.h | 4 ++--
examples/vhost_blk/vhost_blk.c | 2 ++
examples/vhost_blk/vhost_blk.h | 4 ++--
6 files changed, 13 insertions(+), 6 deletions(-)
--
2.24.1
next reply other threads:[~2020-02-05 13:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 13:47 Timothy Redaelli [this message]
2020-02-05 13:47 ` [dpdk-dev] [PATCH 1/3] examples/vhost_blk: " Timothy Redaelli
2020-02-05 15:12 ` Maxime Coquelin
2020-02-05 14:12 ` [dpdk-dev] [PATCH v2 3/3] app/test-pipeline: " Timothy Redaelli
2020-02-05 14:21 ` Dumitrescu, Cristian
2020-02-05 17:05 ` [dpdk-dev] [PATCH 2/3] examples/eventdev_pipeline: " Timothy Redaelli
2020-02-05 17:05 ` [dpdk-dev] [PATCH 3/3] examples/qos_sched: " Timothy Redaelli
2020-03-04 9:37 ` [dpdk-dev] [PATCH 0/3] examples: " David Marchand
2020-03-04 10:17 ` David Marchand
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=cover.1580910264.git.tredaelli@redhat.com \
--to=tredaelli@redhat.com \
--cc=dev@dpdk.org \
--cc=stable@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).