All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Zhu <chaozhu@linux.vnet.ibm.com>
To: dev@dpdk.org
Subject: [PATCH] librte_hash: Fix compile errors on IBM POWER
Date: Wed,  9 Dec 2015 12:11:47 +0800	[thread overview]
Message-ID: <1449634307-24075-1-git-send-email-chaozhu@linux.vnet.ibm.com> (raw)

This patch fixes the compile errors caused by lacking of "size_t" definition in rte_hash.h. The
compile error exists on IBM POWER and ARM (see jerin.jacob@caviumnetworks.com's message).

The errors are like:
In file included from /tmp/dpdk/app/test/test_hash_scaling.c:35:0:
/tmp/dpdk/build/include/rte_hash.h:70:70: error: unknown type name ‘size_t’
 typedef int (*rte_hash_cmp_eq_t)(const void *key1, const void *key2, size_t key_len);
                                                                      ^
/tmp/dpdk/build/include/rte_hash.h:120:48: error: unknown type name ‘rte_hash_cmp_eq_t’
 void rte_hash_set_cmp_func(struct rte_hash *h, rte_hash_cmp_eq_t func);

Signed-off-by: Chao Zhu <chaozhu@linux.vnet.ibm.com>
---
 lib/librte_hash/rte_hash.h |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/lib/librte_hash/rte_hash.h b/lib/librte_hash/rte_hash.h
index 6494ade..85fc416 100644
--- a/lib/librte_hash/rte_hash.h
+++ b/lib/librte_hash/rte_hash.h
@@ -41,6 +41,7 @@
  */
 
 #include <stdint.h>
+#include <stddef.h>
 
 #ifdef __cplusplus
 extern "C" {
-- 
1.7.1

             reply	other threads:[~2015-12-09  4:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09  4:11 Chao Zhu [this message]
2015-12-09  4:40 ` [PATCH] librte_hash: Fix compile errors on IBM POWER Jerin Jacob
2015-12-09 20:22   ` Thomas Monjalon
  -- strict thread matches above, loose matches on Subject: below --
2015-12-08  8:28 Chao Zhu
2015-12-08  9:10 ` Jerin Jacob
2015-12-09  3:54   ` Chao Zhu
2015-12-08 10:05 ` 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=1449634307-24075-1-git-send-email-chaozhu@linux.vnet.ibm.com \
    --to=chaozhu@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.