From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gnutls: update to version 2.10.3
Date: Wed, 13 Jul 2011 22:11:43 +0200 [thread overview]
Message-ID: <1310587903.11691.12.camel@bender> (raw)
In-Reply-To: <87k4bmdrsm.fsf@macbook.be.48ers.dk>
On Wed, 2011-07-13 at 19:16 +0200, Peter Korsgaard wrote:
> >>>>> "Sven" == Sven Neumann <s.neumann@raumfeld.com> writes:
>
> Sven> Update gnutls to the latest release that still uses libgcrypt.
> Sven> Signed-off-by: Sven Neumann <s.neumann@raumfeld.com>
> Sven> ---
> Sven> package/gnutls/gnutls.mk | 5 +++--
> Sven> 1 files changed, 3 insertions(+), 2 deletions(-)
>
> Sven> diff --git a/package/gnutls/gnutls.mk b/package/gnutls/gnutls.mk
> Sven> index 5f31e1e..b62ed3c 100644
> Sven> --- a/package/gnutls/gnutls.mk
> Sven> +++ b/package/gnutls/gnutls.mk
> Sven> @@ -4,11 +4,12 @@
> Sven> #
> Sven> #############################################################
>
> Sven> -GNUTLS_VERSION = 2.8.6
> Sven> +GNUTLS_VERSION = 2.10.3
> Sven> GNUTLS_SOURCE = gnutls-$(GNUTLS_VERSION).tar.bz2
> Sven> GNUTLS_SITE = http://ftp.gnu.org/gnu/gnutls/
> Sven> -GNUTLS_DEPENDENCIES = libgcrypt
> Sven> GNUTLS_CONF_OPT += --without-libgcrypt-prefix
> Sven> GNUTLS_INSTALL_STAGING = YES
>
> Sven> +GNUTLS_DEPENDENCIES = host-pkg-config libglib2 libgcrypt
>
> So it depends on glib now? Then you should select it as well in
> Config.in
Eek, no, it doesn't. Must have been a leftover line from our old gnutls
package that was merged when I updated buildroot. I didn't realize that
it is bogus when I rebased the patches today. Will submit an updated
version tomorrow.
Sven
next prev parent reply other threads:[~2011-07-13 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 17:05 [Buildroot] [PATCH] gnutls: update to version 2.10.3 Sven Neumann
2011-07-13 17:16 ` Peter Korsgaard
2011-07-13 20:11 ` Sven Neumann [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-07-14 7:10 Sven Neumann
2011-07-15 20:10 ` Peter Korsgaard
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=1310587903.11691.12.camel@bender \
--to=s.neumann@raumfeld.com \
--cc=buildroot@busybox.net \
/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