From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>,
"jgrajcia@cisco.com" <jgrajcia@cisco.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Compilation error on master with gcc 9.1
Date: Tue, 6 Aug 2019 16:11:53 +0000 [thread overview]
Message-ID: <BYAPR18MB2424983A12F824604C97C612C8D50@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
CC memif_socket.o
In file included from /home/jerin/dpdk.org/drivers/net/memif/memif_socket.c:26:
In function 'memif_socket_create',
inlined from 'memif_socket_init' at /home/jerin/dpdk.org/drivers/net/memif/memif_socket.c:965:12:
/home/jerin/dpdk.org/drivers/net/memif/rte_eth_memif.h:35:2: error: '%s' directive argument is null [-Werror=format-overflow=]
35 | rte_log(RTE_LOG_ ## level, memif_logtype, \
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
36 | "%s(): " fmt "\n", __func__, ##args)
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/jerin/dpdk.org/drivers/net/memif/memif_socket.c:920:2: note: in expansion of macro 'MIF_LOG'
920 | MIF_LOG(ERR, "%s: Failed to setup socket %s: %s",
| ^~~~~~~
/home/jerin/dpdk.org/drivers/net/memif/memif_socket.c: In function 'memif_socket_init':
/home/jerin/dpdk.org/drivers/net/memif/memif_socket.c:1114:17: note: format string is defined here
1114 | MIF_LOG(ERR, "%s: Failed to register interrupt callback "
| ^~
In file included from /home/jerin/dpdk.org/drivers/net/memif/memif_socket.c:26:
In function 'memif_socket_create',
inlined from 'memif_socket_init' at /home/jerin/dpdk.org/drivers/net/memif/memif_socket.c:965:12:
/home/jerin/dpdk.org/drivers/net/memif/rte_eth_memif.h:35:2: error: '%s' directive argument is null [-Werror=format-overflow=]
35 | rte_log(RTE_LOG_ ## level, memif_logtype, \
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
36 | "%s(): " fmt "\n", __func__, ##args)
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/jerin/dpdk.org/drivers/net/memif/memif_socket.c:920:2: note: in expansion of macro 'MIF_LOG'
920 | MIF_LOG(ERR, "%s: Failed to setup socket %s: %s",
| ^~~~~~~
/home/jerin/dpdk.org/drivers/net/memif/memif_socket.c: In function 'memif_socket_init':
/home/jerin/dpdk.org/drivers/net/memif/memif_socket.c:1114:17: note: format string is defined here
1114 | MIF_LOG(ERR, "%s: Failed to register interrupt callback "
| ^~
$ gcc -v
Using built-in specs.
COLLECT_GCC=/usr/bin/gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-cl
ocale=gnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=gnu --e
nable-gnu-indirect-function --enable-multilib --disable-werror --enable-checking=release --enable-default-pie --enable-default-ssp --enable-cet=auto
Thread model: posix
gcc version 9.1.0 (GCC
reply other threads:[~2019-08-06 16:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BYAPR18MB2424983A12F824604C97C612C8D50@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=jgrajcia@cisco.com \
--cc=thomas@monjalon.net \
/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).