Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] a2jmidid: fix build on musl/ppc (and also a correction on glibc)
Date: Mon, 28 Oct 2019 20:01:49 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15866@inbox.vuxu.org> (raw)

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

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

https://github.com/void-ppc/void-packages a2jmidid
https://github.com/void-linux/void-packages/pull/15866

a2jmidid: fix build on musl/ppc (and also a correction on glibc)


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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-a2jmidid-15866.patch --]
[-- Type: text/x-diff, Size: 1365 bytes --]

From 93024b47c4121c417aa9f748810621e3143b563e Mon Sep 17 00:00:00 2001
From: q66 <daniel@octaforge.org>
Date: Mon, 28 Oct 2019 20:00:45 +0100
Subject: [PATCH] a2jmidid: fix build on musl/ppc (and also a correction on
 glibc)

[ci skip]
---
 srcpkgs/a2jmidid/patches/musl-ppc.patch | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
 create mode 100644 srcpkgs/a2jmidid/patches/musl-ppc.patch

diff --git a/srcpkgs/a2jmidid/patches/musl-ppc.patch b/srcpkgs/a2jmidid/patches/musl-ppc.patch
new file mode 100644
index 00000000000..c16523512ef
--- /dev/null
+++ b/srcpkgs/a2jmidid/patches/musl-ppc.patch
@@ -0,0 +1,18 @@
+This fixes build on ppc32/musl but also fixes incorrect usage of uc_regs
+on glibc (uc_regs is an mcontext_t pointer, you can't index it directly)
+
+--- sigsegv.c
++++ sigsegv.c
+@@ -97,7 +97,11 @@ static void signal_segv(int signum, siginfo_t* info, void*ptr) {
+     for(i = 0; i < NGREG; i++)
+         a2j_error("reg[%02d]       = 0x" REGFORMAT, i,
+ #if defined(__powerpc__) && !defined(__powerpc64__)
+-                ucontext->uc_mcontext.uc_regs[i]
++#if defined(__GLIBC__)
++                ucontext->uc_mcontext.uc_regs->gregs[i]
++#else
++                ucontext->uc_mcontext.gregs[i]
++#endif
+ #elif defined(__powerpc64__)
+                 ucontext->uc_mcontext.gp_regs[i]
+ #elif defined(__sparc__) && defined(__arch64__)

             reply	other threads:[~2019-10-28 19:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-28 19:01 voidlinux-github [this message]
2019-10-28 21:50 ` voidlinux-github
2019-10-29 14:52 ` [PR PATCH] [Merged]: " voidlinux-github

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15866@inbox.vuxu.org \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).