DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.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, 01 Oct 2014 13:56:04 +0200	[thread overview]
Message-ID: <3354420.dnXLPNUCVP@xps13> (raw)
In-Reply-To: <20141001105022.GB21151@hmsreliant.think-freely.org>

2014-10-01 06:50, Neil Horman:
> On Wed, Oct 01, 2014 at 01:27:03PM +0900, mukawa@igel.co.jp wrote:
> > 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.

I don't see any error.
Please Tetsuya, could you describe how you test and what is the error message?

Thanks
-- 
Thomas

  reply	other threads:[~2014-10-01 11:49 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 [this message]
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=3354420.dnXLPNUCVP@xps13 \
    --to=thomas.monjalon@6wind.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).