Skip to contentSkip to conversation

uclibc: update uClibc-ng to latest version

PATCH New Waldemar Brodkorb 2 participants 2 messages Jul 15, 2015

lore
Share & tools
lore

Waldemar Brodkorb

author
#0 lore raw

PATCH 1/2 uclibc: update uClibc-ng to latest version

Fixes gcc 5.1 errors and contains all recent
improvements to Xtensa/ARC NPTL/TLS.

Signed-off-by Waldemar Brodkorb <[email protected]>
---
 package/uclibc/Config.in   |    2 +-
 package/uclibc/uclibc.hash |    4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)
package/uclibc/Config.in +1 -1
index 14f713c..eee5044 100644
@@ -65,7 +65,7 @@ config BR2_UCLIBC_VERSION_STRING
 	string
 	default "0.9.33.2"	if BR2_UCLIBC_VERSION_0_9_33
 	default "arc-2015.06-rc1" if BR2_UCLIBC_VERSION_ARC_GIT
-	default "1.0.3"		if BR2_UCLIBC_VERSION_NG
+	default "1.0.4"		if BR2_UCLIBC_VERSION_NG
 	default BR2_USE_UCLIBC_SNAPSHOT	if BR2_UCLIBC_VERSION_SNAPSHOT
 
 config BR2_UCLIBC_CONFIG
package/uclibc/uclibc.hash +2 -2
index 36fa86f..06e1661 100644
@@ -1,8 +1,8 @@
 # Locally calculated after checking pgp signature
 sha256	62333167b79afb0b25a843513288c67b59547acf653e8fbe62ee64e71ebd1587	uClibc-0.9.33.2.tar.xz
 
-# From http://www.uclibc-ng.org/trac/
-sha256  b4c73fe3e7af4eeabf7510ee66ca85f775c3ed44d20b1bcd30c6ac481dd753cd        uClibc-ng-1.0.3.tar.xz
+# From http://www.uclibc-ng.org/
+sha256  c037dbaea685380c75b112b5503778a90fa95ac524728770131aa17e29474915        uClibc-ng-1.0.4.tar.xz
 
 # No hash for the ARC variant, comes from the github-helper
 none	xxx	uClibc-arc-2015.06-rc1.tar.gz
Signature · 1 line
1.7.10.4
#1 lore raw

PATCH 1/2 uclibc: update uClibc-ng to latest version

Dear Waldemar Brodkorb,

Quoted 8 lines · Waldemar Brodkorb

Fixes gcc 5.1 errors and contains all recent
improvements to Xtensa/ARC NPTL/TLS.

Signed-off-by Waldemar Brodkorb <[email protected]>
---
 package/uclibc/Config.in   |    2 +-
 package/uclibc/uclibc.hash |    4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

Both patches applied, thanks! Note however that we usually combine the bump with the handling of the patches, especially since in general some of the patches are kept accross the bump and adapted accordingly.

In this specific case though it works fine since all 1.0.3 patches have been merged, so the 1.0.4 bump can work on its own, and the 1.0.3 patches removed afterwards.

Thanks!

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com