From: Bo Chen <glbrt.chen@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Compile failed using g++ 4.8.2
Date: Fri, 9 May 2014 11:09:31 +0800 [thread overview]
Message-ID: <CAESsnARdcevcoEKQa0k=REin_psjKao+ecGgd5YouADtTTH4zQ@mail.gmail.com> (raw)
When I use Ubuntu 14.04 to compile my program, the g++ 4.8.2 print the
following error message, that need to add a space around identifier
PRIx64, anyone can help to submit a patch:
/home/bodc/workspace/dpdk/build/dpdk-prefix/src/dpdk/x86_64-default-linuxapp-gcc/include/rte_mempool.h:347:6:
error: invalid suffix on literal; C++11 requires a space between
literal and identifier [-Werror=literal-suffix]
"obj=%p, mempool=%p, cookie=%"PRIx64"\n",
^
/home/bodc/workspace/dpdk/build/dpdk-prefix/src/dpdk/x86_64-default-linuxapp-gcc/include/rte_mempool.h:357:6:
error: invalid suffix on literal; C++11 requires a space between
literal and identifier [-Werror=literal-suffix]
"obj=%p, mempool=%p, cookie=%"PRIx64"\n",
^
/home/bodc/workspace/dpdk/build/dpdk-prefix/src/dpdk/x86_64-default-linuxapp-gcc/include/rte_mempool.h:368:6:
error: invalid suffix on literal; C++11 requires a space between
literal and identifier [-Werror=literal-suffix]
"obj=%p, mempool=%p, cookie=%"PRIx64"\n",
^
/home/bodc/workspace/dpdk/build/dpdk-prefix/src/dpdk/x86_64-default-linuxapp-gcc/include/rte_mempool.h:377:5:
error: invalid suffix on literal; C++11 requires a space between
literal and identifier [-Werror=literal-suffix]
"obj=%p, mempool=%p, cookie=%"PRIx64"\n",
^
In file included from
/home/bodc/workspace/dpdk/build/dpdk-prefix/src/dpdk/x86_64-default-linuxapp-gcc/include/rte_ethdev.h:177:0,
from /home/bodc/workspace/tcproxy/src/comm/packet.cc:9:
/home/bodc/workspace/dpdk/build/dpdk-prefix/src/dpdk/x86_64-default-linuxapp-gcc/include/rte_pci.h:95:21:
error: invalid suffix on literal; C++11 requires a space between
literal and identifier [-Werror=literal-suffix]
#define PCI_PRI_FMT "%.4"PRIx16":%.2"PRIx8":%.2"PRIx8".%"PRIx8
^
/home/bodc/workspace/dpdk/build/dpdk-prefix/src/dpdk/x86_64-default-linuxapp-gcc/include/rte_pci.h:95:32:
error: invalid suffix on literal; C++11 requires a space between
literal and identifier [-Werror=literal-suffix]
#define PCI_PRI_FMT "%.4"PRIx16":%.2"PRIx8":%.2"PRIx8".%"PRIx8
^
/home/bodc/workspace/dpdk/build/dpdk-prefix/src/dpdk/x86_64-default-linuxapp-gcc/include/rte_pci.h:95:43:
error: invalid suffix on literal; C++11 requires a space between
literal and identifier [-Werror=literal-suffix]
#define PCI_PRI_FMT "%.4"PRIx16":%.2"PRIx8":%.2"PRIx8".%"PRIx8
^
/home/bodc/workspace/dpdk/build/dpdk-prefix/src/dpdk/x86_64-default-linuxapp-gcc/include/rte_pci.h:95:54:
error: invalid suffix on literal; C++11 requires a space between
literal and identifier [-Werror=literal-suffix]
#define PCI_PRI_FMT "%.4"PRIx16":%.2"PRIx8":%.2"PRIx8".%"PRIx8
^
/home/bodc/workspace/dpdk/build/dpdk-prefix/src/dpdk/x86_64-default-linuxapp-gcc/include/rte_pci.h:98:27:
error: invalid suffix on literal; C++11 requires a space between
literal and identifier [-Werror=literal-suffix]
#define PCI_SHORT_PRI_FMT "%.2"PRIx8":%.2"PRIx8".%"PRIx8
^
/home/bodc/workspace/dpdk/build/dpdk-prefix/src/dpdk/x86_64-default-linuxapp-gcc/include/rte_pci.h:98:37:
error: invalid suffix on literal; C++11 requires a space between
literal and identifier [-Werror=literal-suffix]
#define PCI_SHORT_PRI_FMT "%.2"PRIx8":%.2"PRIx8".%"PRIx8
^
/home/bodc/workspace/dpdk/build/dpdk-prefix/src/dpdk/x86_64-default-linuxapp-gcc/include/rte_pci.h:98:48:
error: invalid suffix on literal; C++11 requires a space between
literal and identifier [-Werror=literal-suffix]
#define PCI_SHORT_PRI_FMT "%.2"PRIx8":%.2"PRIx8".%"PRIx8
reply other threads:[~2014-05-09 3:09 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='CAESsnARdcevcoEKQa0k=REin_psjKao+ecGgd5YouADtTTH4zQ@mail.gmail.com' \
--to=glbrt.chen@gmail.com \
--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).