From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] ntp: Do not use an RPATH.
Date: Fri, 21 Oct 2016 13:11:50 +0200 [thread overview]
Message-ID: <1477048310-17051-1-git-send-email-stefan.schantl@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 693 bytes --]
Fixes #11243.
Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
---
ntp/ntp.nm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/ntp/ntp.nm b/ntp/ntp.nm
index 780ad01..ad4b046 100644
--- a/ntp/ntp.nm
+++ b/ntp/ntp.nm
@@ -6,7 +6,7 @@
name = ntp
version = %{ver_major}.8
ver_major = 4.2
-release = 2
+release = 3
groups = System/Daemons
url = http://www.ntp.org/
@@ -49,6 +49,7 @@ build
configure_options += \
--sysconfdir=%{sysconfdir}/ntp/crypto \
--with-openssl-libdir=%{libdir} \
+ --without-rpath \
--enable-all-clocks \
--enable-parse-clocks \
--enable-ntp-signd=%{localstatedir}/run/ntp_signd
--
2.7.4
next reply other threads:[~2016-10-21 11:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 11:11 Stefan Schantl [this message]
2016-10-21 13:08 ` Michael Tremer
2016-10-28 11:26 ` Stefan Schantl
2017-01-12 9:30 ` Stefan Schantl
2017-01-12 9:32 ` [PATCHv2] ntp: Do not use a RPATH Stefan Schantl
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=1477048310-17051-1-git-send-email-stefan.schantl@ipfire.org \
--to=stefan.schantl@ipfire.org \
--cc=development@lists.ipfire.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