From: "Jürgen Beisert" <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [RFC] standalone udev fails to build with recent GCC toolchain
Date: Mon, 6 Jan 2014 10:20:15 +0100 [thread overview]
Message-ID: <201401061020.15990.jbe@pengutronix.de> (raw)
Linking the standalone udev fails due to the missing librt when using
a more recent GCC toolchain to compile the package. It seems in earlier
versions of the GCC toolchain librt comes in from a different library udev is
linked against.
How to fix it? Adding a patch to its buildsystem to force the librt when
linking udev? Or more simply with the following approach?
diff --git a/rules/udev.make b/rules/udev.make
index dcdf79c..735c1c2 100644
--- a/rules/udev.make
+++ b/rules/udev.make
@@ -44,6 +44,7 @@ UDEV_LICENSE := GPLv2
#
UDEV_CONF_ENV := \
$(CROSS_ENV) \
+ LIBS=-lrt \
CPPFLAGS="-I$(KERNEL_HEADERS_INCLUDE_DIR) $(CROSS_CPPFLAGS)"
UDEV_CONF_TOOL := autoconf
jbe
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
reply other threads:[~2014-01-06 9:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201401061020.15990.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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