Github messages for voidlinux
 help / color / mirror / Atom feed
* [PR PATCH] musl: update to 1.1.23.
@ 2019-07-18 13:10 voidlinux-github
  2019-07-18 13:28 ` voidlinux-github
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: voidlinux-github @ 2019-07-18 13:10 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 336 bytes --]

There is a new pull request by Gottox against master on the void-packages repository

https://github.com/Gottox/void-packages musl-1.1.23
https://github.com/void-linux/void-packages/pull/13210

musl: update to 1.1.23.
@q66 please check for ppc.

A patch file from https://github.com/void-linux/void-packages/pull/13210.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-musl-1.1.23-13210.patch --]
[-- Type: application/text/x-diff, Size: 5530 bytes --]

From a709b83e35a6a6fd10415930ac9aeb1c87c669c8 Mon Sep 17 00:00:00 2001
From: Enno Boland <gottox@voidlinux.org>
Date: Thu, 18 Jul 2019 14:40:54 +0200
Subject: [PATCH] musl: update to 1.1.23.

---
 srcpkgs/musl/patches/mo_lookup.patch          | 19 --------
 .../patches/ppc64-vrregset-t-fix-layout.patch | 45 -------------------
 .../patches/ppc64-vrregset-t-vrregs-fix.patch | 29 ------------
 srcpkgs/musl/template                         |  6 +--
 4 files changed, 3 insertions(+), 96 deletions(-)
 delete mode 100644 srcpkgs/musl/patches/mo_lookup.patch
 delete mode 100644 srcpkgs/musl/patches/ppc64-vrregset-t-fix-layout.patch
 delete mode 100644 srcpkgs/musl/patches/ppc64-vrregset-t-vrregs-fix.patch

diff --git a/srcpkgs/musl/patches/mo_lookup.patch b/srcpkgs/musl/patches/mo_lookup.patch
deleted file mode 100644
index c23eaf33bc3..00000000000
--- a/srcpkgs/musl/patches/mo_lookup.patch
+++ /dev/null
@@ -1,19 +0,0 @@
-Do not crash with a NULL pointer dereference when dcngettext()
-is called with NULL msgid[12] arguments.
-
-Fix for https://github.com/void-linux/void-packages/issues/12042
-and probably others.
-
-	--xtraeme
-
---- src/locale/__mo_lookup.c.orig	2019-06-26 09:55:36.843012674 +0200
-+++ src/locale/__mo_lookup.c	2019-06-26 09:56:11.529443955 +0200
-@@ -13,7 +13,7 @@ const char *__mo_lookup(const void *p, s
- 	uint32_t b = 0, n = swapc(mo[2], sw);
- 	uint32_t o = swapc(mo[3], sw);
- 	uint32_t t = swapc(mo[4], sw);
--	if (n>=size/4 || o>=size-4*n || t>=size-4*n || ((o|t)%4))
-+	if (!s || n>=size/4 || o>=size-4*n || t>=size-4*n || ((o|t)%4))
- 		return 0;
- 	o/=4;
- 	t/=4;
diff --git a/srcpkgs/musl/patches/ppc64-vrregset-t-fix-layout.patch b/srcpkgs/musl/patches/ppc64-vrregset-t-fix-layout.patch
deleted file mode 100644
index 5ca68a35aaf..00000000000
--- a/srcpkgs/musl/patches/ppc64-vrregset-t-fix-layout.patch
+++ /dev/null
@@ -1,45 +0,0 @@
-commit 3c59a868956636bc8adafb1b168d090897692532
-Author: Rich Felker <dalias@aerifal.cx>
-Date:   Wed May 22 15:17:12 2019 -0400
-
-    fix vrregset_t layout and member naming on powerpc64
-    
-    the mistaken layout seems to have been adapted from 32-bit powerpc,
-    where vscr and vrsave are packed into the same 128-bit slot in a way
-    that looks like it relies on non-overlapping-ness of the value bits in
-    big endian.
-    
-    the powerpc64 port accounted for the fact that the 64-bit ABI puts
-    each in its own 128-bit slot, but ordered them incorrectly (matching
-    the bit order used on the 32-bit ABI), and failed to account for vscr
-    being padded according to endianness so that it can be accessed via
-    vector moves.
-    
-    in addition to ABI layout, our definition used different logical
-    member layout/naming from glibc, where vscr is a structure to
-    facilitate access as a 32-bit word or a 128-bit vector. the
-    inconsistency here was unintentional, so fix it.
-
-diff --git a/arch/powerpc64/bits/signal.h b/arch/powerpc64/bits/signal.h
-index 34693a68..94c7a327 100644
---- arch/powerpc64/bits/signal.h
-+++ arch/powerpc64/bits/signal.h
-@@ -17,10 +17,14 @@ typedef struct {
- 
- typedef struct {
- 	unsigned __int128 vrregs[32];
--	unsigned _pad[3];
--	unsigned vrsave;
--	unsigned vscr;
--	unsigned _pad2[3];
-+	struct {
-+#if __BIG_ENDIAN__
-+		unsigned _pad[3], vscr_word;
-+#else
-+		unsigned vscr_word, _pad[3];
-+#endif
-+	} vscr;
-+	unsigned vrsave, _pad[3];
- } vrregset_t;
- 
- typedef struct sigcontext {
diff --git a/srcpkgs/musl/patches/ppc64-vrregset-t-vrregs-fix.patch b/srcpkgs/musl/patches/ppc64-vrregset-t-vrregs-fix.patch
deleted file mode 100644
index 0d2664e6c97..00000000000
--- a/srcpkgs/musl/patches/ppc64-vrregset-t-vrregs-fix.patch
+++ /dev/null
@@ -1,29 +0,0 @@
-commit ac304227bb3ea1787d581f17d76a5f5f3abff51f
-Author: Rich Felker <dalias@aerifal.cx>
-Date:   Wed May 22 18:28:32 2019 -0400
-
-    make powerpc64 vrregset_t logical layout match expected API
-    
-    between v2 and v3 of the powerpc64 port patch, the change was made
-    from a 32x4 array of 32-bit unsigned ints for vrregs[] to a 32-element
-    array of __int128. this mismatches the API applications working with
-    mcontext_t expect from glibc, and seems to have been motivated by a
-    misinterpretation of a comment on how aarch64 did things as a
-    suggestion to do the same on powerpc64.
-
-diff --git a/arch/powerpc64/bits/signal.h b/arch/powerpc64/bits/signal.h
-index 94c7a327..2cc0604c 100644
---- arch/powerpc64/bits/signal.h
-+++ arch/powerpc64/bits/signal.h
-@@ -16,7 +16,10 @@ typedef struct {
- } fpregset_t;
- 
- typedef struct {
--	unsigned __int128 vrregs[32];
-+#ifdef __GNUC__
-+	__attribute__((__aligned__(16)))
-+#endif
-+	unsigned vrregs[32][4];
- 	struct {
- #if __BIG_ENDIAN__
- 		unsigned _pad[3], vscr_word;
diff --git a/srcpkgs/musl/template b/srcpkgs/musl/template
index 4a312725d60..5a267c59ff0 100644
--- a/srcpkgs/musl/template
+++ b/srcpkgs/musl/template
@@ -1,7 +1,7 @@
 # Template file for 'musl'.
 pkgname=musl
-version=1.1.22
-revision=4
+version=1.1.23
+revision=1
 archs="*-musl"
 build_style=gnu-configure
 configure_args="--prefix=/usr --disable-gcc-wrapper"
@@ -12,7 +12,7 @@ maintainer="Juan RP <xtraeme@voidlinux.org>"
 license="MIT"
 homepage="http://www.musl-libc.org/"
 distfiles="http://www.musl-libc.org/releases/musl-${version}.tar.gz"
-checksum=8b0941a48d2f980fd7036cfbd24aa1d414f03d9a0652ecbd5ec5c7ff1bee29e3
+checksum=8a0feb41cef26c97dde382c014e68b9bb335c094bbc1356f6edaaf6b79bd14aa
 
 nostrip_files="libc.so"
 shlib_provides="libc.so"

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: musl: update to 1.1.23.
  2019-07-18 13:10 [PR PATCH] musl: update to 1.1.23 voidlinux-github
@ 2019-07-18 13:28 ` voidlinux-github
  2019-07-19  7:54 ` [PR PATCH] [Updated] " voidlinux-github
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: voidlinux-github @ 2019-07-18 13:28 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1782 bytes --]

New comment by xtraeme on void-packages repository

https://github.com/void-linux/void-packages/pull/13210#issuecomment-512815741
Comment:
The mo lookup patch I think is still necessary. Otherwise gimp and others
will segfault with a non default locale.

El jue., 18 jul. 2019 15:10, Enno Boland <notifications@github.com>
escribió:

> @q66 <https://github.com/q66> please check for ppc.
> ------------------------------
> You can view, comment on, or merge this pull request online at:
>
>   https://github.com/void-linux/void-packages/pull/13210
> Commit Summary
>
>    - musl: update to 1.1.23.
>
> File Changes
>
>    - *D* srcpkgs/musl/patches/mo_lookup.patch
>    <https://github.com/void-linux/void-packages/pull/13210/files#diff-0>
>    (19)
>    - *D* srcpkgs/musl/patches/ppc64-vrregset-t-fix-layout.patch
>    <https://github.com/void-linux/void-packages/pull/13210/files#diff-1>
>    (45)
>    - *D* srcpkgs/musl/patches/ppc64-vrregset-t-vrregs-fix.patch
>    <https://github.com/void-linux/void-packages/pull/13210/files#diff-2>
>    (29)
>    - *M* srcpkgs/musl/template
>    <https://github.com/void-linux/void-packages/pull/13210/files#diff-3>
>    (6)
>
> Patch Links:
>
>    - https://github.com/void-linux/void-packages/pull/13210.patch
>    - https://github.com/void-linux/void-packages/pull/13210.diff
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/void-linux/void-packages/pull/13210?email_source=notifications&email_token=AAGR7KNZT67GCGXHY4HUNYDQABTTHA5CNFSM4IE2SNXKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G777QAA>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAGR7KJ5IQYMBOZG6NF3LJ3QABTTHANCNFSM4IE2SNXA>
> .
>


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PR PATCH] [Updated] musl: update to 1.1.23.
  2019-07-18 13:10 [PR PATCH] musl: update to 1.1.23 voidlinux-github
  2019-07-18 13:28 ` voidlinux-github
@ 2019-07-19  7:54 ` voidlinux-github
  2019-07-19  7:54 ` voidlinux-github
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: voidlinux-github @ 2019-07-19  7:54 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 341 bytes --]

There is an updated pull request by Gottox against master on the void-packages repository

https://github.com/Gottox/void-packages musl-1.1.23
https://github.com/void-linux/void-packages/pull/13210

musl: update to 1.1.23.
@q66 please check for ppc.

A patch file from https://github.com/void-linux/void-packages/pull/13210.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-musl-1.1.23-13210.patch --]
[-- Type: application/text/x-diff, Size: 4515 bytes --]

From dc161a1e572b8f8d4f2e6e1acbc1934857f11b71 Mon Sep 17 00:00:00 2001
From: Enno Boland <gottox@voidlinux.org>
Date: Thu, 18 Jul 2019 14:40:54 +0200
Subject: [PATCH] musl: update to 1.1.23.

---
 .../patches/ppc64-vrregset-t-fix-layout.patch | 45 -------------------
 .../patches/ppc64-vrregset-t-vrregs-fix.patch | 29 ------------
 srcpkgs/musl/template                         |  6 +--
 3 files changed, 3 insertions(+), 77 deletions(-)
 delete mode 100644 srcpkgs/musl/patches/ppc64-vrregset-t-fix-layout.patch
 delete mode 100644 srcpkgs/musl/patches/ppc64-vrregset-t-vrregs-fix.patch

diff --git a/srcpkgs/musl/patches/ppc64-vrregset-t-fix-layout.patch b/srcpkgs/musl/patches/ppc64-vrregset-t-fix-layout.patch
deleted file mode 100644
index 5ca68a35aaf..00000000000
--- a/srcpkgs/musl/patches/ppc64-vrregset-t-fix-layout.patch
+++ /dev/null
@@ -1,45 +0,0 @@
-commit 3c59a868956636bc8adafb1b168d090897692532
-Author: Rich Felker <dalias@aerifal.cx>
-Date:   Wed May 22 15:17:12 2019 -0400
-
-    fix vrregset_t layout and member naming on powerpc64
-    
-    the mistaken layout seems to have been adapted from 32-bit powerpc,
-    where vscr and vrsave are packed into the same 128-bit slot in a way
-    that looks like it relies on non-overlapping-ness of the value bits in
-    big endian.
-    
-    the powerpc64 port accounted for the fact that the 64-bit ABI puts
-    each in its own 128-bit slot, but ordered them incorrectly (matching
-    the bit order used on the 32-bit ABI), and failed to account for vscr
-    being padded according to endianness so that it can be accessed via
-    vector moves.
-    
-    in addition to ABI layout, our definition used different logical
-    member layout/naming from glibc, where vscr is a structure to
-    facilitate access as a 32-bit word or a 128-bit vector. the
-    inconsistency here was unintentional, so fix it.
-
-diff --git a/arch/powerpc64/bits/signal.h b/arch/powerpc64/bits/signal.h
-index 34693a68..94c7a327 100644
---- arch/powerpc64/bits/signal.h
-+++ arch/powerpc64/bits/signal.h
-@@ -17,10 +17,14 @@ typedef struct {
- 
- typedef struct {
- 	unsigned __int128 vrregs[32];
--	unsigned _pad[3];
--	unsigned vrsave;
--	unsigned vscr;
--	unsigned _pad2[3];
-+	struct {
-+#if __BIG_ENDIAN__
-+		unsigned _pad[3], vscr_word;
-+#else
-+		unsigned vscr_word, _pad[3];
-+#endif
-+	} vscr;
-+	unsigned vrsave, _pad[3];
- } vrregset_t;
- 
- typedef struct sigcontext {
diff --git a/srcpkgs/musl/patches/ppc64-vrregset-t-vrregs-fix.patch b/srcpkgs/musl/patches/ppc64-vrregset-t-vrregs-fix.patch
deleted file mode 100644
index 0d2664e6c97..00000000000
--- a/srcpkgs/musl/patches/ppc64-vrregset-t-vrregs-fix.patch
+++ /dev/null
@@ -1,29 +0,0 @@
-commit ac304227bb3ea1787d581f17d76a5f5f3abff51f
-Author: Rich Felker <dalias@aerifal.cx>
-Date:   Wed May 22 18:28:32 2019 -0400
-
-    make powerpc64 vrregset_t logical layout match expected API
-    
-    between v2 and v3 of the powerpc64 port patch, the change was made
-    from a 32x4 array of 32-bit unsigned ints for vrregs[] to a 32-element
-    array of __int128. this mismatches the API applications working with
-    mcontext_t expect from glibc, and seems to have been motivated by a
-    misinterpretation of a comment on how aarch64 did things as a
-    suggestion to do the same on powerpc64.
-
-diff --git a/arch/powerpc64/bits/signal.h b/arch/powerpc64/bits/signal.h
-index 94c7a327..2cc0604c 100644
---- arch/powerpc64/bits/signal.h
-+++ arch/powerpc64/bits/signal.h
-@@ -16,7 +16,10 @@ typedef struct {
- } fpregset_t;
- 
- typedef struct {
--	unsigned __int128 vrregs[32];
-+#ifdef __GNUC__
-+	__attribute__((__aligned__(16)))
-+#endif
-+	unsigned vrregs[32][4];
- 	struct {
- #if __BIG_ENDIAN__
- 		unsigned _pad[3], vscr_word;
diff --git a/srcpkgs/musl/template b/srcpkgs/musl/template
index 4a312725d60..5a267c59ff0 100644
--- a/srcpkgs/musl/template
+++ b/srcpkgs/musl/template
@@ -1,7 +1,7 @@
 # Template file for 'musl'.
 pkgname=musl
-version=1.1.22
-revision=4
+version=1.1.23
+revision=1
 archs="*-musl"
 build_style=gnu-configure
 configure_args="--prefix=/usr --disable-gcc-wrapper"
@@ -12,7 +12,7 @@ maintainer="Juan RP <xtraeme@voidlinux.org>"
 license="MIT"
 homepage="http://www.musl-libc.org/"
 distfiles="http://www.musl-libc.org/releases/musl-${version}.tar.gz"
-checksum=8b0941a48d2f980fd7036cfbd24aa1d414f03d9a0652ecbd5ec5c7ff1bee29e3
+checksum=8a0feb41cef26c97dde382c014e68b9bb335c094bbc1356f6edaaf6b79bd14aa
 
 nostrip_files="libc.so"
 shlib_provides="libc.so"

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PR PATCH] [Updated] musl: update to 1.1.23.
  2019-07-18 13:10 [PR PATCH] musl: update to 1.1.23 voidlinux-github
  2019-07-18 13:28 ` voidlinux-github
  2019-07-19  7:54 ` [PR PATCH] [Updated] " voidlinux-github
@ 2019-07-19  7:54 ` voidlinux-github
  2019-07-19  8:09 ` voidlinux-github
  2019-07-24 10:59 ` [PR PATCH] [Merged]: " voidlinux-github
  4 siblings, 0 replies; 6+ messages in thread
From: voidlinux-github @ 2019-07-19  7:54 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 341 bytes --]

There is an updated pull request by Gottox against master on the void-packages repository

https://github.com/Gottox/void-packages musl-1.1.23
https://github.com/void-linux/void-packages/pull/13210

musl: update to 1.1.23.
@q66 please check for ppc.

A patch file from https://github.com/void-linux/void-packages/pull/13210.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-musl-1.1.23-13210.patch --]
[-- Type: application/text/x-diff, Size: 4515 bytes --]

From dc161a1e572b8f8d4f2e6e1acbc1934857f11b71 Mon Sep 17 00:00:00 2001
From: Enno Boland <gottox@voidlinux.org>
Date: Thu, 18 Jul 2019 14:40:54 +0200
Subject: [PATCH] musl: update to 1.1.23.

---
 .../patches/ppc64-vrregset-t-fix-layout.patch | 45 -------------------
 .../patches/ppc64-vrregset-t-vrregs-fix.patch | 29 ------------
 srcpkgs/musl/template                         |  6 +--
 3 files changed, 3 insertions(+), 77 deletions(-)
 delete mode 100644 srcpkgs/musl/patches/ppc64-vrregset-t-fix-layout.patch
 delete mode 100644 srcpkgs/musl/patches/ppc64-vrregset-t-vrregs-fix.patch

diff --git a/srcpkgs/musl/patches/ppc64-vrregset-t-fix-layout.patch b/srcpkgs/musl/patches/ppc64-vrregset-t-fix-layout.patch
deleted file mode 100644
index 5ca68a35aaf..00000000000
--- a/srcpkgs/musl/patches/ppc64-vrregset-t-fix-layout.patch
+++ /dev/null
@@ -1,45 +0,0 @@
-commit 3c59a868956636bc8adafb1b168d090897692532
-Author: Rich Felker <dalias@aerifal.cx>
-Date:   Wed May 22 15:17:12 2019 -0400
-
-    fix vrregset_t layout and member naming on powerpc64
-    
-    the mistaken layout seems to have been adapted from 32-bit powerpc,
-    where vscr and vrsave are packed into the same 128-bit slot in a way
-    that looks like it relies on non-overlapping-ness of the value bits in
-    big endian.
-    
-    the powerpc64 port accounted for the fact that the 64-bit ABI puts
-    each in its own 128-bit slot, but ordered them incorrectly (matching
-    the bit order used on the 32-bit ABI), and failed to account for vscr
-    being padded according to endianness so that it can be accessed via
-    vector moves.
-    
-    in addition to ABI layout, our definition used different logical
-    member layout/naming from glibc, where vscr is a structure to
-    facilitate access as a 32-bit word or a 128-bit vector. the
-    inconsistency here was unintentional, so fix it.
-
-diff --git a/arch/powerpc64/bits/signal.h b/arch/powerpc64/bits/signal.h
-index 34693a68..94c7a327 100644
---- arch/powerpc64/bits/signal.h
-+++ arch/powerpc64/bits/signal.h
-@@ -17,10 +17,14 @@ typedef struct {
- 
- typedef struct {
- 	unsigned __int128 vrregs[32];
--	unsigned _pad[3];
--	unsigned vrsave;
--	unsigned vscr;
--	unsigned _pad2[3];
-+	struct {
-+#if __BIG_ENDIAN__
-+		unsigned _pad[3], vscr_word;
-+#else
-+		unsigned vscr_word, _pad[3];
-+#endif
-+	} vscr;
-+	unsigned vrsave, _pad[3];
- } vrregset_t;
- 
- typedef struct sigcontext {
diff --git a/srcpkgs/musl/patches/ppc64-vrregset-t-vrregs-fix.patch b/srcpkgs/musl/patches/ppc64-vrregset-t-vrregs-fix.patch
deleted file mode 100644
index 0d2664e6c97..00000000000
--- a/srcpkgs/musl/patches/ppc64-vrregset-t-vrregs-fix.patch
+++ /dev/null
@@ -1,29 +0,0 @@
-commit ac304227bb3ea1787d581f17d76a5f5f3abff51f
-Author: Rich Felker <dalias@aerifal.cx>
-Date:   Wed May 22 18:28:32 2019 -0400
-
-    make powerpc64 vrregset_t logical layout match expected API
-    
-    between v2 and v3 of the powerpc64 port patch, the change was made
-    from a 32x4 array of 32-bit unsigned ints for vrregs[] to a 32-element
-    array of __int128. this mismatches the API applications working with
-    mcontext_t expect from glibc, and seems to have been motivated by a
-    misinterpretation of a comment on how aarch64 did things as a
-    suggestion to do the same on powerpc64.
-
-diff --git a/arch/powerpc64/bits/signal.h b/arch/powerpc64/bits/signal.h
-index 94c7a327..2cc0604c 100644
---- arch/powerpc64/bits/signal.h
-+++ arch/powerpc64/bits/signal.h
-@@ -16,7 +16,10 @@ typedef struct {
- } fpregset_t;
- 
- typedef struct {
--	unsigned __int128 vrregs[32];
-+#ifdef __GNUC__
-+	__attribute__((__aligned__(16)))
-+#endif
-+	unsigned vrregs[32][4];
- 	struct {
- #if __BIG_ENDIAN__
- 		unsigned _pad[3], vscr_word;
diff --git a/srcpkgs/musl/template b/srcpkgs/musl/template
index 4a312725d60..5a267c59ff0 100644
--- a/srcpkgs/musl/template
+++ b/srcpkgs/musl/template
@@ -1,7 +1,7 @@
 # Template file for 'musl'.
 pkgname=musl
-version=1.1.22
-revision=4
+version=1.1.23
+revision=1
 archs="*-musl"
 build_style=gnu-configure
 configure_args="--prefix=/usr --disable-gcc-wrapper"
@@ -12,7 +12,7 @@ maintainer="Juan RP <xtraeme@voidlinux.org>"
 license="MIT"
 homepage="http://www.musl-libc.org/"
 distfiles="http://www.musl-libc.org/releases/musl-${version}.tar.gz"
-checksum=8b0941a48d2f980fd7036cfbd24aa1d414f03d9a0652ecbd5ec5c7ff1bee29e3
+checksum=8a0feb41cef26c97dde382c014e68b9bb335c094bbc1356f6edaaf6b79bd14aa
 
 nostrip_files="libc.so"
 shlib_provides="libc.so"

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: musl: update to 1.1.23.
  2019-07-18 13:10 [PR PATCH] musl: update to 1.1.23 voidlinux-github
                   ` (2 preceding siblings ...)
  2019-07-19  7:54 ` voidlinux-github
@ 2019-07-19  8:09 ` voidlinux-github
  2019-07-24 10:59 ` [PR PATCH] [Merged]: " voidlinux-github
  4 siblings, 0 replies; 6+ messages in thread
From: voidlinux-github @ 2019-07-19  8:09 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 207 bytes --]

New comment by Gottox on void-packages repository

https://github.com/void-linux/void-packages/pull/13210#issuecomment-513136601
Comment:
Yea, Talked in #musl about the issue. For now I reapplied the patch.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PR PATCH] [Merged]: musl: update to 1.1.23.
  2019-07-18 13:10 [PR PATCH] musl: update to 1.1.23 voidlinux-github
                   ` (3 preceding siblings ...)
  2019-07-19  8:09 ` voidlinux-github
@ 2019-07-24 10:59 ` voidlinux-github
  4 siblings, 0 replies; 6+ messages in thread
From: voidlinux-github @ 2019-07-24 10:59 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 182 bytes --]

There's a merged pull request on the void-packages repository

musl: update to 1.1.23.
https://github.com/void-linux/void-packages/pull/13210
Description: @q66 please check for ppc.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2019-07-24 10:59 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-18 13:10 [PR PATCH] musl: update to 1.1.23 voidlinux-github
2019-07-18 13:28 ` voidlinux-github
2019-07-19  7:54 ` [PR PATCH] [Updated] " voidlinux-github
2019-07-19  7:54 ` voidlinux-github
2019-07-19  8:09 ` voidlinux-github
2019-07-24 10:59 ` [PR PATCH] [Merged]: " voidlinux-github

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).