DPDK patches and discussions
 help / color / mirror / Atom feed
From: Cunming Liang <cunming.liang@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v1 1/2] eal/linux: fix symbol missing in version map
Date: Wed, 25 Feb 2015 11:39:48 +0800	[thread overview]
Message-ID: <1424835589-18122-2-git-send-email-cunming.liang@intel.com> (raw)
In-Reply-To: <1424835589-18122-1-git-send-email-cunming.liang@intel.com>

As per_lcore__socket_id and rte_sys_gettid are missing in version map,
it causes compiling error when CONFIG_RTE_BUILD_SHARED_LIB is enabled.

Signed-off-by: Cunming Liang <cunming.liang@intel.com>
---
 lib/librte_eal/linuxapp/eal/rte_eal_version.map | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/lib/librte_eal/linuxapp/eal/rte_eal_version.map b/lib/librte_eal/linuxapp/eal/rte_eal_version.map
index c207cee..17515a9 100644
--- a/lib/librte_eal/linuxapp/eal/rte_eal_version.map
+++ b/lib/librte_eal/linuxapp/eal/rte_eal_version.map
@@ -10,6 +10,7 @@ DPDK_2.0 {
 	pci_driver_list;
 	per_lcore__lcore_id;
 	per_lcore__rte_errno;
+	per_lcore__socket_id;
 	rte_cpu_check_supported;
 	rte_cpu_get_flag_enabled;
 	rte_cycles_vmware_tsc_map;
@@ -83,6 +84,7 @@ DPDK_2.0 {
 	rte_snprintf;
 	rte_strerror;
 	rte_strsplit;
+	rte_sys_gettid;
 	rte_thread_get_affinity;
 	rte_thread_set_affinity;
 	rte_vlog;
-- 
1.8.1.4

  reply	other threads:[~2015-02-25  3:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25  3:39 [dpdk-dev] [PATCH v1 0/2] eal: " Cunming Liang
2015-02-25  3:39 ` Cunming Liang [this message]
2015-02-25  3:39 ` [dpdk-dev] [PATCH v1 2/2] eal/bsd: " Cunming Liang
2015-02-25  4:08 ` [dpdk-dev] [PATCH v1 0/2] eal: " Tetsuya Mukawa
2015-02-25  8:14 ` Mcnamara, John
2015-02-25  9:07   ` Thomas Monjalon
2015-02-25 12:30 ` Neil Horman
2015-02-25 13:39   ` Thomas Monjalon
2015-02-25 14:34     ` Neil Horman

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=1424835589-18122-2-git-send-email-cunming.liang@intel.com \
    --to=cunming.liang@intel.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).