From: "Wiles, Roger Keith" <keith.wiles@windriver.com>
To: Gal Sagie <gal.sagie@gmail.com>
Cc: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] problem with rte_hash
Date: Sun, 9 Jun 2013 17:16:54 +0000 [thread overview]
Message-ID: <4FF8E6AB-221F-4784-A7FF-F7E54147012A@windriver.com> (raw)
In-Reply-To: <CAG9LJa63E0cmRKTQQwmWNU9YmW=2znijR-HZYBS+pcfGx9_XnA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
Hi
Could this problem be a circular linker problem, try duplicating the libraries on the link line again and see if that fixes the problem. In GCC you also have the option --start-group and --end-group to force the linker to resolve relink these libs until all of the dependences have been resolved.
In the mk/rte.app.mk makefile fragment is an example of these options.
I hope this helps.
Thank you, ++Keith
-------------------------------
Keith Wiles
Principal Technologist for Networking
cell 972-213-5533
Wind River Systems
On Jun 9, 2013, at 9:52 AM, Gal Sagie <gal.sagie@gmail.com<mailto:gal.sagie@gmail.com>> wrote:
rte_cpu_get_flag_enabled
[-- Attachment #2: Type: text/html, Size: 2110 bytes --]
next prev parent reply other threads:[~2013-06-09 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-09 14:52 Gal Sagie
2013-06-09 17:16 ` Wiles, Roger Keith [this message]
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=4FF8E6AB-221F-4784-A7FF-F7E54147012A@windriver.com \
--to=keith.wiles@windriver.com \
--cc=dev@dpdk.org \
--cc=gal.sagie@gmail.com \
/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).