From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] mpfr: update to 3.1.4 (bugfix release, released on 6 March 2016)
Date: Tue, 22 Mar 2016 22:07:40 +0000 [thread overview]
Message-ID: <1458684460.30749.72.camel@ipfire.org> (raw)
In-Reply-To: <1457525784-18663-1-git-send-email-marcel.lorenz@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2147 bytes --]
Hi,
you should *always* try to build the packages before you commit and send the
patch.
This one doesn't build because the patch does not apply. If it is removed, the
build will run through. Please resend.
Best,
-Michael
On Wed, 2016-03-09 at 13:16 +0100, Marcel Lorenz wrote:
> My mpfr 3.1.3 patch of this morning is already outdated...
> http://www.mpfr.org/mpfr-3.1.4/
>
> Signed-off-by: Marcel Lorenz <marcel.lorenz(a)ipfire.org>
>
> ---
> config/rootfiles/common/mpfr | 4 ++--
> lfs/mpfr | 5 ++---
> 2 files changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/config/rootfiles/common/mpfr b/config/rootfiles/common/mpfr
> index 1e33e05..0153810 100644
> --- a/config/rootfiles/common/mpfr
> +++ b/config/rootfiles/common/mpfr
> @@ -4,7 +4,7 @@
> #usr/lib/libmpfr.la
> #usr/lib/libmpfr.so
> usr/lib/libmpfr.so.4
> -usr/lib/libmpfr.so.4.1.3
> +usr/lib/libmpfr.so.4.1.4
> #usr/share/doc/mpfr
> #usr/share/doc/mpfr/AUTHORS
> #usr/share/doc/mpfr/BUGS
> @@ -19,4 +19,4 @@ usr/lib/libmpfr.so.4.1.3
> #usr/share/doc/mpfr/examples/rndo-add.c
> #usr/share/doc/mpfr/examples/sample.c
> #usr/share/doc/mpfr/examples/version.c
> -#usr/share/info/mpfr.info
> \ No newline at end of file
> +#usr/share/info/mpfr.info
> diff --git a/lfs/mpfr b/lfs/mpfr
> index bdf083b..2ebec12 100644
> --- a/lfs/mpfr
> +++ b/lfs/mpfr
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 3.1.3
> +VER = 3.1.4
>
> THISAPP = mpfr-$(VER)
> DL_FILE = $(THISAPP).tar.xz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_MD5 = 6969398cd2fbc56a6af570b5273c56a9
> +$(DL_FILE)_MD5 = 064b2c18185038e404a401b830d59be8
>
> install : $(TARGET)
>
> @@ -70,7 +70,6 @@ $(subst %,%_MD5,$(objects)) :
> $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
> @$(PREBUILD)
> @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE)
> cd $(DIR_APP) && $(CONFIGURE_ARGS) ./configure --prefix=/usr \
> --enable-thread-safe --disable-nls
> cd $(DIR_APP) && make $(MAKETUNING)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-22 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 12:16 Marcel Lorenz
2016-03-22 22:07 ` Michael Tremer [this message]
2016-03-23 6:40 ` Marcel Lorenz
2016-03-23 11:24 ` Michael Tremer
2016-03-23 19:41 ` Marcel Lorenz
2016-03-29 14:01 ` Michael Tremer
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=1458684460.30749.72.camel@ipfire.org \
--to=michael.tremer@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