From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uclibc: update uClibc-ng to 1.0.12
Date: Mon, 1 Feb 2016 17:20:22 +0100 [thread overview]
Message-ID: <20160201162022.GA8040@waldemar-brodkorb.de> (raw)
New release contains a security fix for the resolver library parts.
It contains exp10(), so some patches in buildroot might be obsolete,
when the buildroot toolchains are rebuild.
It also contains a fix for the symbol clashing with bind9.
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
package/uclibc/Config.in | 2 +-
package/uclibc/uclibc.hash | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/uclibc/Config.in b/package/uclibc/Config.in
index 1e4d892..b4d7bd8 100644
--- a/package/uclibc/Config.in
+++ b/package/uclibc/Config.in
@@ -57,7 +57,7 @@ config BR2_USE_UCLIBC_SNAPSHOT
config BR2_UCLIBC_VERSION_STRING
string
default "0.9.33.2" if BR2_UCLIBC_VERSION_0_9_33
- default "1.0.11" if BR2_UCLIBC_VERSION_NG
+ default "1.0.12" if BR2_UCLIBC_VERSION_NG
default BR2_USE_UCLIBC_SNAPSHOT if BR2_UCLIBC_VERSION_SNAPSHOT
config BR2_UCLIBC_CONFIG
diff --git a/package/uclibc/uclibc.hash b/package/uclibc/uclibc.hash
index 9acb82e..cb95468 100644
--- a/package/uclibc/uclibc.hash
+++ b/package/uclibc/uclibc.hash
@@ -2,7 +2,7 @@
sha256 62333167b79afb0b25a843513288c67b59547acf653e8fbe62ee64e71ebd1587 uClibc-0.9.33.2.tar.xz
# From http://www.uclibc-ng.org/
-sha256 2fdc6b9015f8049be0eb12a5e3e446de471fb80061115afd8d72ea582cb22b74 uClibc-ng-1.0.11.tar.xz
+sha256 c238b300356b2638432e023076293f29935094108a2714ad1762b76015fae729 uClibc-ng-1.0.12.tar.xz
# No hash for this git snapshot
none xxx uClibc-7bf35c8b7d4a1f97174eb49f47f33946b282114c.tar.gz
--
1.7.10.4
next reply other threads:[~2016-02-01 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 16:20 Waldemar Brodkorb [this message]
2016-02-01 18:24 ` [Buildroot] [PATCH] uclibc: update uClibc-ng to 1.0.12 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=20160201162022.GA8040@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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