From: "Xu, Qian Q" <qian.q.xu@intel.com>
To: Nagaprabhanjan Bellaru <nagp.lists@gmail.com>,
"users@dpdk.org" <users@dpdk.org>
Cc: "Chen, WeichunX" <weichunx.chen@intel.com>,
"Wei, FangfangX" <fangfangx.wei@intel.com>,
"Lu, PeipeiX" <peipeix.lu@intel.com>
Subject: Re: [dpdk-users] Compiling DPDK 16.07 with shared option is failing..
Date: Thu, 10 Nov 2016 08:21:22 +0000 [thread overview]
Message-ID: <82F45D86ADE5454A95A89742C8D1410E3924F745@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <CABDVJk87mBwwixi78fUZPr6oDebCr5h=0Lqd9-wRpFUd-SmDWw@mail.gmail.com>
We have tested the configuration, and it works on our platform. I wonder what's your OS/Kernel/gcc version.
-----Original Message-----
From: users [mailto:users-bounces@dpdk.org] On Behalf Of Nagaprabhanjan Bellaru
Sent: Wednesday, November 9, 2016 8:34 PM
To: users@dpdk.org
Subject: [dpdk-users] Compiling DPDK 16.07 with shared option is failing..
Hi,
I am compiling DPDK with "CONFIG_RTE_BUILD_SHARED_LIB=y". However, when I compile, it is failing at:
--
gcc -pie -fPIC
-L/home/ubuntu/development/libfwdd/src/platform/vpp/vpp/build-root/install-vpp_debug-native/dpdk/lib
-Wl,-g -shared rte_sched.o rte_red.o rte_approx.o rte_reciprocal.o -z defs -lm -lrt -lrte_eal -lrte_mempool -lrte_mbuf -lrte_timer
-Wl,-soname,librte_sched.so.1.1 -o librte_sched.so.1.1
/usr/bin/ld: cannot find -lrte_timer
--
I can see that librte_timer is not compiled yet, however librte_sched depends on it - is there any workaround for this issue? Can I change the order somewhere?
Thanks,
-nagp
prev parent reply other threads:[~2016-11-10 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 12:34 Nagaprabhanjan Bellaru
2016-11-10 5:07 ` Nagaprabhanjan Bellaru
2016-11-10 8:18 ` Thomas Monjalon
2016-11-10 8:23 ` Nagaprabhanjan Bellaru
2016-11-10 12:28 ` Nagaprabhanjan Bellaru
2016-11-10 8:21 ` Xu, Qian Q [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=82F45D86ADE5454A95A89742C8D1410E3924F745@shsmsx102.ccr.corp.intel.com \
--to=qian.q.xu@intel.com \
--cc=fangfangx.wei@intel.com \
--cc=nagp.lists@gmail.com \
--cc=peipeix.lu@intel.com \
--cc=users@dpdk.org \
--cc=weichunx.chen@intel.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).