From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] ntp: Do not use an RPATH.
Date: Fri, 28 Oct 2016 13:26:38 +0200 [thread overview]
Message-ID: <1477653998.4746.0.camel@ipfire.org> (raw)
In-Reply-To: <1477055310.9760.8.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1971 bytes --]
Hello Michael,
tested with "pakfire-builder build ntp.nm -m release" and worked fine.
Best regards,
-Stefan
> This won't compile...
>
> Applying patches...
> Applying /usr/src/packages/ntp-4.2.8-3.ip3.src/patches/ntpstat-0.2-
> 1-clksrc.patch (-N -p1)...
> can't find file to patch at input line 4
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --------------------------
> >
> > diff -up ntp-4.2.4p7/ntpstat-0.2/ntpstat.c.ntpstat ntp-
> > 4.2.4p7/ntpstat-0.2/ntpstat.c
> > --- ntp-4.2.4p7/ntpstat-0.2/ntpstat.c.ntpstat 2002-06-10
> > 08:02:12.000000000 +0200
> > +++ ntp-4.2.4p7/ntpstat-0.2/ntpstat.c 2009-07-20
> > 12:22:35.000000000 +0200
> --------------------------
> File to patch:
> Skip this patch? [y]
> Skipping patch.
> 1 out of 1 hunk ignored
> Command exited with an error: ['bash', '--login', '-c',
> '/tmp/tmpaBqkiM']
>
> An error has occured when running Pakfire.
>
> Error message:
> BuildError: An unhandled error occured.
>
> Further description:
> Build command has failed.
>
> On Fri, 2016-10-21 at 13:11 +0200, Stefan Schantl wrote:
> >
> > 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-10-28 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 11:11 Stefan Schantl
2016-10-21 13:08 ` Michael Tremer
2016-10-28 11:26 ` Stefan Schantl [this message]
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=1477653998.4746.0.camel@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