From: Gal Sagie <gal.sagie@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] problem with rte_hash
Date: Sun, 9 Jun 2013 17:52:49 +0300 [thread overview]
Message-ID: <CAG9LJa63E0cmRKTQQwmWNU9YmW=2znijR-HZYBS+pcfGx9_XnA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 510 bytes --]
Hello all,
I am trying to do an example of using rte_hash, i am getting the following
linker problem:
/main.o -lrte_eal -lpthread -lethdev -lrte_malloc -lrte_mbuf
-lrte_mempool -lrte_pmd_igb -lrte_pmd_ixgbe -lrte_ring -lrte_timer
-lrte_hash
/home/gal/dpdk/x86_64-default-linuxapp-gcc/lib/librte_hash.a(rte_hash.o):
In function `rte_hash_create':
rte_hash.c:(.text+0x6f8): undefined reference to `rte_cpu_get_flag_enabled'
collect2: ld returned 1 exit status
anyone familiar with that?
Thanks in advance!
[-- Attachment #2: Type: text/html, Size: 581 bytes --]
next reply other threads:[~2013-06-09 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-09 14:52 Gal Sagie [this message]
2013-06-09 17:16 ` Wiles, Roger Keith
2013-06-10 4:14 ` Gal Sagie
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='CAG9LJa63E0cmRKTQQwmWNU9YmW=2znijR-HZYBS+pcfGx9_XnA@mail.gmail.com' \
--to=gal.sagie@gmail.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).