From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-devel/m4/files/
Date: Sun, 13 Mar 2022 22:23:42 +0000 (UTC) [thread overview]
Message-ID: <1647210210.ebd6285d85cb1e5b921f68fd5f6cd571feb1603b.sam@gentoo> (raw)
commit: ebd6285d85cb1e5b921f68fd5f6cd571feb1603b
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 13 22:23:11 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Mar 13 22:23:30 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ebd6285d
sys-devel/m4: add link to upstream gnulib/musl/ppc patch
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-devel/m4/files/ppc-musl.patch | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/sys-devel/m4/files/ppc-musl.patch b/sys-devel/m4/files/ppc-musl.patch
index d7d8255a444a..4aff0ba1cf5c 100644
--- a/sys-devel/m4/files/ppc-musl.patch
+++ b/sys-devel/m4/files/ppc-musl.patch
@@ -1,7 +1,8 @@
-Needed to fix build on ppc + musl. Doesn't seem to yet be in upstream gnulib.
+Needed to fix build on ppc + musl. Should pop up in next gnulib sync in release (different patch).
https://www.openwall.com/lists/musl/2017/11/05/2
https://github.com/void-linux/void-packages/blob/master/srcpkgs/grep/patches/ppc-musl.patch
+https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=2d830e4a792fcd9f614ed08a7f18584b8b21d23b
--- a/lib/sigsegv.c
+++ b/lib/sigsegv.c
@@ -221,8 +221,10 @@ int libsigsegv_version = LIBSIGSEGV_VERSION;
next reply other threads:[~2022-03-13 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 22:23 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-09 15:07 [gentoo-commits] repo/gentoo:master commit in: sys-devel/m4/files/ Sam James
2021-11-17 4:34 Sam James
2021-03-31 19:51 Conrad Kostecki
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=1647210210.ebd6285d85cb1e5b921f68fd5f6cd571feb1603b.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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