From: "Liang, Cunming" <cunming.liang@intel.com>
To: Tetsuya Mukawa <mukawa@igel.co.jp>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Missing symbol error
Date: Wed, 25 Feb 2015 03:09:39 +0000 [thread overview]
Message-ID: <D0158A423229094DA7ABF71CF2FA0DA3118DE829@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <54ED3827.4060700@igel.co.jp>
Hi,
You're right, it's missing in the version map.
Will send path to fix it.
Thanks.
> -----Original Message-----
> From: Tetsuya Mukawa [mailto:mukawa@igel.co.jp]
> Sent: Wednesday, February 25, 2015 10:49 AM
> To: dev@dpdk.org
> Cc: Liang, Cunming
> Subject: Missing symbol error
>
> Hi,
>
> I've got following error when I enable CONFIG_RTE_BUILD_SHARED_LIB.
>
> dpdk/x86_64-native-linuxapp-gcc/lib/libethdev.so: undefined reference to
> `per_lcore__socket_id'
> collect2: error: ld returned 1 exit status
> make[5]: *** [dump_cfg] Error 1
> make[4]: *** [dump_cfg] Error 2
> make[4]: *** Waiting for unfinished jobs....
>
>
> It seems after applying below commit, this issue is occurred.
> 8baacdd... eal: apply thread affinity by assigned cpuset
>
> Thanks,
> Tetsuya
prev parent reply other threads:[~2015-02-25 3:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 2:49 Tetsuya Mukawa
2015-02-25 3:09 ` Liang, Cunming [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=D0158A423229094DA7ABF71CF2FA0DA3118DE829@shsmsx102.ccr.corp.intel.com \
--to=cunming.liang@intel.com \
--cc=dev@dpdk.org \
--cc=mukawa@igel.co.jp \
/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).