From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Stefan Puiu <stefan.puiu@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Stefan Puiu <spuiu@ixiacom.com>
Subject: Re: [dpdk-dev] [PATCH] Fix compilation error when compiling with clang-3.4 in C++11 mode: in C++11 concatenated string literals need to have a space in between.
Date: Fri, 20 Feb 2015 08:19:06 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D89727261905@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1424379569-15851-2-git-send-email-stefan.puiu@gmail.com>
Hi Stefan,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Stefan Puiu
> Sent: Thursday, February 19, 2015 8:59 PM
> To: dev@dpdk.org
> Cc: Stefan Puiu
> Subject: [dpdk-dev] [PATCH] Fix compilation error when compiling with
> clang-3.4 in C++11 mode: in C++11 concatenated string literals need to have a
> space in between.
>
> From: Stefan Puiu <spuiu@ixiacom.com>
>
> Sample error message:
> dpdk/include/rte_pci.h:96:26: error: invalid suffix on literal; C++11 requires a
> space between literal and identifier [-Wreserved-user-defined-literal]
You forgot to include "Signed-off".
Pablo
> ---
> lib/librte_eal/common/include/rte_pci.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lib/librte_eal/common/include/rte_pci.h
> b/lib/librte_eal/common/include/rte_pci.h
> index 66ed793..12ae5a7 100644
> --- a/lib/librte_eal/common/include/rte_pci.h
> +++ b/lib/librte_eal/common/include/rte_pci.h
> @@ -93,10 +93,10 @@ extern struct pci_device_list pci_device_list; /**<
> Global list of PCI devices.
> #define SYSFS_PCI_DEVICES "/sys/bus/pci/devices"
>
> /** Formatting string for PCI device identifier: Ex: 0000:00:01.0 */
> -#define PCI_PRI_FMT "%.4"PRIx16":%.2"PRIx8":%.2"PRIx8".%"PRIx8
> +#define PCI_PRI_FMT "%.4" PRIx16 ":%.2" PRIx8 ":%.2" PRIx8 ".%" PRIx8
>
> /** Short formatting string, without domain, for PCI device: Ex: 00:01.0 */
> -#define PCI_SHORT_PRI_FMT "%.2"PRIx8":%.2"PRIx8".%"PRIx8
> +#define PCI_SHORT_PRI_FMT "%.2" PRIx8 ":%.2" PRIx8 ".%" PRIx8
>
> /** Nb. of values in PCI device identifier format string. */
> #define PCI_FMT_NVAL 4
> --
> 1.7.9.5
next prev parent reply other threads:[~2015-02-20 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 20:59 [dpdk-dev] [PATCH] Fix C++11 compilation error with rte_pci.h Stefan Puiu
2015-02-19 20:59 ` [dpdk-dev] [PATCH] Fix compilation error when compiling with clang-3.4 in C++11 mode: in C++11 concatenated string literals need to have a space in between Stefan Puiu
2015-02-20 8:19 ` De Lara Guarch, Pablo [this message]
2015-02-20 8:34 ` Stefan Puiu
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=E115CCD9D858EF4F90C690B0DCB4D89727261905@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=spuiu@ixiacom.com \
--cc=stefan.puiu@gmail.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).