From: Yi Lu <luyi68@live.com>
To: david.marchand@6wind.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] eal: fix compile error in eal_timer.c
Date: Sun, 3 Jan 2016 22:49:12 +0800 [thread overview]
Message-ID: <BLU436-SMTP157815B37FD696F25A704E3A4F10@phx.gbl> (raw)
Error message:
/root/dpdk-2.2.0/lib/librte_eal/linuxapp/eal/eal_timer.c: In function ‘rte_eal_hpet_init’:
/root/dpdk-2.2.0/lib/librte_eal/linuxapp/eal/eal_timer.c:222:2: error: implicit declaration of function ‘rte_thread_setname’ [-Werror=implicit-function-declaration]
ret = rte_thread_setname(msb_inc_thread_id, thread_name);
^
/root/dpdk-2.2.0/lib/librte_eal/linuxapp/eal/eal_timer.c:222:2: error: nested extern declaration of ‘rte_thread_setname’ [-Werror=nested-externs]
cc1: all warnings being treated as errors
Fixes: badb3688ffa8 ("eal/linux: fix build with glibc < 2.12")
Signed-off-by: Yi Lu <luyi68@live.com>
---
lib/librte_eal/linuxapp/eal/eal_timer.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/librte_eal/linuxapp/eal/eal_timer.c b/lib/librte_eal/linuxapp/eal/eal_timer.c
index 9ceff33..bcadf09 100644
--- a/lib/librte_eal/linuxapp/eal/eal_timer.c
+++ b/lib/librte_eal/linuxapp/eal/eal_timer.c
@@ -50,6 +50,7 @@
#include <rte_memory.h>
#include <rte_memzone.h>
#include <rte_eal.h>
+#include <rte_lcore.h>
#include <rte_debug.h>
#include "eal_private.h"
--
1.8.3.1
next reply other threads:[~2016-01-03 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-03 14:49 Yi Lu [this message]
2016-01-04 9:01 ` David Marchand
2016-01-28 14:16 ` [dpdk-dev] [PATCH] eal: fix compile error in eal_timer.c caused by hpet 卢 毅
2016-03-02 16:45 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2016-01-03 14:46 [dpdk-dev] [PATCH] eal: fix compile error in eal_timer.c luyi68
2016-01-03 14:43 Yi Lu
2016-01-03 14:35 Yi Lu
2016-01-03 14:22 Yi Lu
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=BLU436-SMTP157815B37FD696F25A704E3A4F10@phx.gbl \
--to=luyi68@live.com \
--cc=david.marchand@6wind.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).