DPDK patches and discussions
 help / color / mirror / Atom feed
From: Takuya ASADA <syuu@cloudius-systems.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [RFC PATCHv3 4/7] eal: Add extern C on eal_private.h
Date: Tue,  7 Apr 2015 03:58:08 +0900	[thread overview]
Message-ID: <1428346691-14894-5-git-send-email-syuu@cloudius-systems.com> (raw)
In-Reply-To: <1428346691-14894-1-git-send-email-syuu@cloudius-systems.com>

This is required to link with OSv EAL.

Signed-off-by: Takuya ASADA <syuu@cloudius-systems.com>
---
 lib/librte_eal/common/eal_private.h | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/lib/librte_eal/common/eal_private.h b/lib/librte_eal/common/eal_private.h
index 4acf5a0..80b3d44 100644
--- a/lib/librte_eal/common/eal_private.h
+++ b/lib/librte_eal/common/eal_private.h
@@ -34,6 +34,10 @@
 #ifndef _EAL_PRIVATE_H_
 #define _EAL_PRIVATE_H_
 
+#ifdef __cplusplus
+extern "C" {
+#endif
+
 #include <stdio.h>
 
 /**
@@ -232,4 +236,8 @@ int rte_eal_dev_init(void);
  */
 int rte_eal_check_module(const char *module_name);
 
+#ifdef __cplusplus
+}
+#endif
+
 #endif /* _EAL_PRIVATE_H_ */
-- 
2.1.0

  parent reply	other threads:[~2015-04-06 18:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06 18:58 [dpdk-dev] [RFC PATCHv3 0/7] add OSv support Takuya ASADA
2015-04-06 18:58 ` [dpdk-dev] [RFC PATCHv3 1/7] mk: support compiling C++ code Takuya ASADA
2015-04-06 18:58 ` [dpdk-dev] [RFC PATCHv3 2/7] eal: Add extern C on eal_hugepages.h Takuya ASADA
2015-04-06 18:58 ` [dpdk-dev] [RFC PATCHv3 3/7] eal: Add extern C on eal_thread.h Takuya ASADA
2015-04-06 18:58 ` Takuya ASADA [this message]
2015-04-06 18:58 ` [dpdk-dev] [RFC PATCHv3 5/7] add OSv support Takuya ASADA
2015-04-06 18:58 ` [dpdk-dev] [RFC PATCHv3 6/7] app/test: support OSv Takuya ASADA
2015-04-06 18:58 ` [dpdk-dev] [RFC PATCHv3 7/7] doc: Add Getting Started Guide for OSv Takuya ASADA
2015-06-18 14:09   ` Mcnamara, John
2015-04-20 18:37 ` [dpdk-dev] [RFC PATCHv3 0/7] add OSv support Takuya ASADA
2015-07-08 23:35   ` Thomas Monjalon

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=1428346691-14894-5-git-send-email-syuu@cloudius-systems.com \
    --to=syuu@cloudius-systems.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).