From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] mk: fix static link with glibc < 2.17
Date: Mon, 18 Jul 2016 11:43:45 +0200 [thread overview]
Message-ID: <1468835025-3333-1-git-send-email-thomas.monjalon@6wind.com> (raw)
There is an error when linking static EAL library with an application:
eal_alarm.c:(.text+0xd7): undefined reference to `clock_gettime'
eal_alarm.c:(.text+0x20f): undefined reference to `clock_gettime'
eal_timer.c:(.text+0x108): undefined reference to `clock_gettime'
eal_timer.c:(.text+0x146): undefined reference to `clock_gettime'
The function clock_gettime() is in librt for old glibc.
Fixes: 281948b4753e ("mk: fix missing librt dependencies")
Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
---
mk/rte.app.mk | 1 +
1 file changed, 1 insertion(+)
diff --git a/mk/rte.app.mk b/mk/rte.app.mk
index 886dbdd..eb28e11 100644
--- a/mk/rte.app.mk
+++ b/mk/rte.app.mk
@@ -151,6 +151,7 @@ _LDLIBS-y += --no-whole-archive
ifeq ($(CONFIG_RTE_BUILD_SHARED_LIB),n)
# The static libraries do not know their dependencies.
# So linking with static library requires explicit dependencies.
+_LDLIBS-$(CONFIG_RTE_LIBRTE_EAL) += -lrt
_LDLIBS-$(CONFIG_RTE_LIBRTE_SCHED) += -lm
_LDLIBS-$(CONFIG_RTE_LIBRTE_SCHED) += -lrt
_LDLIBS-$(CONFIG_RTE_LIBRTE_METER) += -lm
--
2.7.0
next reply other threads:[~2016-07-18 9:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 9:43 Thomas Monjalon [this message]
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
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=1468835025-3333-1-git-send-email-thomas.monjalon@6wind.com \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
/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).