From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 10/10] libgcrypt: version bump 1.5.3 -> 1.6.3
Date: Sat, 21 Mar 2015 18:17:25 +0100 [thread overview]
Message-ID: <20150321171725.GL20453@pengutronix.de> (raw)
In-Reply-To: <1425637560-23901-10-git-send-email-h.feurstein@gmail.com>
On Fri, Mar 06, 2015 at 11:26:00AM +0100, Hubert Feurstein wrote:
> Signed-off-by: Hubert Feurstein <h.feurstein@gmail.com>
When updating to a new version, please check for new configure options.
I usually diff the output of './configure --help' to see what changed and
update the options accordingly.
In this case I see some hardware accel options. I think there are runtime
checks (please verify) so we can enable those unconditionally. For NEON we
have an options (PTXCONF_NEON) so that should be used.
Michael
> ---
> rules/libgcrypt.make | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/rules/libgcrypt.make b/rules/libgcrypt.make
> index b700487..fe3e474 100644
> --- a/rules/libgcrypt.make
> +++ b/rules/libgcrypt.make
> @@ -17,8 +17,8 @@ PACKAGES-$(PTXCONF_LIBGCRYPT) += libgcrypt
> #
> # Paths and names
> #
> -LIBGCRYPT_VERSION := 1.5.3
> -LIBGCRYPT_MD5 := 993159b2924ae7b0e4eaff0743c2db35
> +LIBGCRYPT_VERSION := 1.6.3
> +LIBGCRYPT_MD5 := 4262c3aadf837500756c2051a5c4ae5e
> LIBGCRYPT := libgcrypt-$(LIBGCRYPT_VERSION)
> LIBGCRYPT_SUFFIX := tar.bz2
> LIBGCRYPT_URL := http://artfiles.org/gnupg.org/libgcrypt/$(LIBGCRYPT).$(LIBGCRYPT_SUFFIX) ftp://ftp.gnupg.org/gcrypt/libgcrypt/$(LIBGCRYPT).$(LIBGCRYPT_SUFFIX)
> --
> 2.3.0
>
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-03-21 17:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 10:25 [ptxdist] [PATCH 01/10] chrony: version bump 1.29 -> 1.31 Hubert Feurstein
2015-03-06 10:25 ` [ptxdist] [PATCH 02/10] util-linux-ng: add fstrim option Hubert Feurstein
2015-03-26 8:48 ` Michael Olbrich
2015-03-06 10:25 ` [ptxdist] [PATCH 03/10] util-linux-ng: add dmesg option Hubert Feurstein
2015-03-26 8:49 ` Michael Olbrich
2015-03-06 10:25 ` [ptxdist] [PATCH 04/10] ethtool: version bump 3.0 -> 3.18 Hubert Feurstein
2015-03-26 8:51 ` Michael Olbrich
2015-03-06 10:25 ` [ptxdist] [PATCH 05/10] ethtool: add license information Hubert Feurstein
2015-03-26 8:51 ` Michael Olbrich
2015-03-06 10:25 ` [ptxdist] [PATCH 06/10] libksba: version bump 1.0.7 -> 1.3.2 Hubert Feurstein
2015-03-26 8:51 ` Michael Olbrich
2015-03-06 10:25 ` [ptxdist] [PATCH 07/10] libksba: add license information Hubert Feurstein
2015-03-26 8:52 ` Michael Olbrich
2015-03-06 10:25 ` [ptxdist] [PATCH 08/10] libassuan: version bump 2.0.0 -> 2.2.0 Hubert Feurstein
2015-03-26 8:53 ` Michael Olbrich
2015-03-06 10:25 ` [ptxdist] [PATCH 09/10] libassuan: add license information Hubert Feurstein
2015-03-26 8:53 ` Michael Olbrich
2015-03-06 10:26 ` [ptxdist] [PATCH 10/10] libgcrypt: version bump 1.5.3 -> 1.6.3 Hubert Feurstein
2015-03-21 17:17 ` Michael Olbrich [this message]
2015-03-26 8:50 ` [ptxdist] [PATCH 01/10] chrony: version bump 1.29 -> 1.31 Michael Olbrich
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=20150321171725.GL20453@pengutronix.de \
--to=m.olbrich@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