From: Tetsuya Mukawa <mukawa@igel.co.jp>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] Fix linking errors when CONFIG_RTE_BUILD_SHARED_LIB is enabled
Date: Thu, 02 Oct 2014 10:43:52 +0900 [thread overview]
Message-ID: <542CADD8.9070402@igel.co.jp> (raw)
In-Reply-To: <20141001105022.GB21151@hmsreliant.think-freely.org>
(2014/10/01 19:50), Neil Horman wrote:
> I'm not sure why thats necesecary. We add a --start-group/--end-group pair
> halfway through this makefile. If we just encompassed the entire set of
> libraries in that group, order would be irrelevant.
I haven't known the options. Thanks.
Anyway, I understand I shouldn't change link order, but should check why
'--start-group/--end-group' doesn't work on my environment.
I will describe more in the email for Thomas.
Regards,
Tetsuya
> Neil
>
>> Signed-off-by: Tetsuya Mukawa <mukawa@igel.co.jp>
>> ---
>> mk/rte.app.mk | 16 ++++++++--------
>> 1 file changed, 8 insertions(+), 8 deletions(-)
>>
>> diff --git a/mk/rte.app.mk b/mk/rte.app.mk
>> index 34dff2a..172ba4d 100644
>> --- a/mk/rte.app.mk
>> +++ b/mk/rte.app.mk
>> @@ -121,10 +121,6 @@ endif
>>
>> LDLIBS += --start-group
>>
>> -ifeq ($(CONFIG_RTE_LIBRTE_KVARGS),y)
>> -LDLIBS += -lrte_kvargs
>> -endif
>> -
>> ifeq ($(CONFIG_RTE_LIBRTE_MBUF),y)
>> LDLIBS += -lrte_mbuf
>> endif
>> @@ -137,6 +133,10 @@ ifeq ($(CONFIG_RTE_LIBRTE_ETHER),y)
>> LDLIBS += -lethdev
>> endif
>>
>> +ifeq ($(CONFIG_RTE_LIBRTE_EAL),y)
>> +LDLIBS += -lrte_eal
>> +endif
>> +
>> ifeq ($(CONFIG_RTE_LIBRTE_MALLOC),y)
>> LDLIBS += -lrte_malloc
>> endif
>> @@ -158,10 +158,6 @@ ifeq ($(CONFIG_RTE_LIBGLOSS),y)
>> LDLIBS += -lgloss
>> endif
>>
>> -ifeq ($(CONFIG_RTE_LIBRTE_EAL),y)
>> -LDLIBS += -lrte_eal
>> -endif
>> -
>> ifeq ($(CONFIG_RTE_LIBRTE_CMDLINE),y)
>> LDLIBS += -lrte_cmdline
>> endif
>> @@ -174,6 +170,10 @@ ifeq ($(CONFIG_RTE_LIBRTE_PMD_BOND),y)
>> LDLIBS += -lrte_pmd_bond
>> endif
>>
>> +ifeq ($(CONFIG_RTE_LIBRTE_KVARGS),y)
>> +LDLIBS += -lrte_kvargs
>> +endif
>> +
>> ifeq ($(CONFIG_RTE_LIBRTE_PMD_XENVIRT),y)
>> LDLIBS += -lrte_pmd_xenvirt
>> LDLIBS += -lxenstore
>> --
>> 1.9.1
>>
>>
next prev parent reply other threads:[~2014-10-02 1:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 4:27 mukawa
2014-10-01 10:50 ` Neil Horman
2014-10-01 11:56 ` Thomas Monjalon
2014-10-02 2:48 ` Tetsuya Mukawa
2014-10-02 8:12 ` Sergio Gonzalez Monroy
2014-10-02 8:28 ` Tetsuya Mukawa
2014-10-02 8:53 ` Sergio Gonzalez Monroy
2014-10-02 9:05 ` Tetsuya Mukawa
2014-10-03 11:11 ` Sergio Gonzalez Monroy
2014-10-02 1:43 ` Tetsuya Mukawa [this message]
2014-10-02 2:46 ` Matthew Hall
2014-10-02 3:44 ` Tetsuya Mukawa
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=542CADD8.9070402@igel.co.jp \
--to=mukawa@igel.co.jp \
--cc=dev@dpdk.org \
--cc=nhorman@tuxdriver.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).