DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gal Sagie <gal.sagie@gmail.com>
To: "Wiles, Roger Keith" <keith.wiles@windriver.com>
Cc: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] problem with rte_hash
Date: Mon, 10 Jun 2013 07:14:23 +0300	[thread overview]
Message-ID: <CAG9LJa6uThQ_yydsXy00zVXcymu+7rz1_z9ZLReDdQa89S=YhQ@mail.gmail.com> (raw)
In-Reply-To: <4FF8E6AB-221F-4784-A7FF-F7E54147012A@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 907 bytes --]

Hi,

Thanks for the help, i got it fixed (just moved the rte_hash library before
the rte_eal and it solved it)

On Sun, Jun 9, 2013 at 8:16 PM, Wiles, Roger Keith <
keith.wiles@windriver.com> wrote:

>  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> wrote:
>
> rte_cpu_get_flag_enabled
>
>
>


-- 
Best Regards ,

The G.

[-- Attachment #2: Type: text/html, Size: 2235 bytes --]

      reply	other threads:[~2013-06-10  4:14 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
2013-06-10  4:14   ` Gal Sagie [this message]

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='CAG9LJa6uThQ_yydsXy00zVXcymu+7rz1_z9ZLReDdQa89S=YhQ@mail.gmail.com' \
    --to=gal.sagie@gmail.com \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@windriver.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).