DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Azarewicz, PiotrX T" <piotrx.t.azarewicz@intel.com>
Cc: "Gu, YongjieX" <yongjiex.gu@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mk: fix static link with glibc < 2.17
Date: Mon, 25 Jul 2016 14:37:22 +0200	[thread overview]
Message-ID: <12890652.mUoZe8QKBF@xps13> (raw)
In-Reply-To: <4837007523CC9A4B9414D20C13DE6E64136EC83D@IRSMSX102.ger.corp.intel.com>

2016-07-25 11:13, Azarewicz, PiotrX T:
> > The problem is that -lrt appears before -lrte_eal.
> > The question is: where does it come from?
> > It is even before _LDLIBS-y += -L$(RTE_SDK_BIN)/lib... mystery
> 
> root cause:
> commit	c7cda4d8b4ea9cb0f209dda36882d225354b1db9

The error is seen after this commit, yes.
But I would not say it is the root cause.
The root cause is adding -lrt before other libs:
	281948b4753e ("mk: fix missing librt dependencies")

> and my workaround is:
> /app/test/Makefile
> 
>  ifeq ($(CONFIG_RTE_LIBRTE_SCHED),y)
> -LDLIBS += -lrt
>  SRCS-y += test_red.c
>  SRCS-y += test_sched.c
>  endif

Yes it is what I've done in this patch:
	http://dpdk.org/patch/15008

  reply	other threads:[~2016-07-25 12:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18  9:43 Thomas Monjalon
2016-07-20  1:19 ` Gu, YongjieX
2016-07-21  8:22   ` Thomas Monjalon
2016-07-22 13:38     ` Azarewicz, PiotrX T
2016-07-22 13:43       ` Thomas Monjalon
2016-07-22 14:07         ` Azarewicz, PiotrX T
2016-07-22 14:14           ` Thomas Monjalon
2016-07-22 14:47             ` Azarewicz, PiotrX T
2016-07-22 15:05               ` Thomas Monjalon
2016-07-25 11:13                 ` Azarewicz, PiotrX T
2016-07-25 12:37                   ` Thomas Monjalon [this message]
2016-07-26  7:06                     ` Azarewicz, PiotrX T

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=12890652.mUoZe8QKBF@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=piotrx.t.azarewicz@intel.com \
    --cc=yongjiex.gu@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).