From: Neil Horman <nhorman@tuxdriver.com>
To: mukawa@igel.co.jp
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] Fix linking errors when CONFIG_RTE_BUILD_SHARED_LIB is enabled
Date: Wed, 1 Oct 2014 06:50:22 -0400 [thread overview]
Message-ID: <20141001105022.GB21151@hmsreliant.think-freely.org> (raw)
In-Reply-To: <1412137623-18817-1-git-send-email-mukawa@igel.co.jp>
On Wed, Oct 01, 2014 at 01:27:03PM +0900, mukawa@igel.co.jp wrote:
> From: Tetsuya Mukawa <mukawa@igel.co.jp>
>
> When CONFIG_RTE_BUILD_SHARED_LIB is enabled, linking errors occured
> while compiling. It seems those errors are caused by wrong link order
> of some libraries. The patch fixes it like following.
>
> 1. librte_eal
> 2. librte_malloc
> 3. librte_mempool
> 4. librte_ring
> 5. librte_pmd_bond
> 6. librte_kvargs
>
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.
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-01 10:43 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 [this message]
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
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=20141001105022.GB21151@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.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).