From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] libucontext: switch upstream + update to 0.10
Date: Fri, 08 May 2020 12:56:11 +0200 [thread overview]
Message-ID: <20200508105611.FoNPNT632ZLYCZFU6MqVg0RBVAHKEeLHAnpV-fLcka0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21743@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 472 bytes --]
There is an updated pull request by pullmoll against master on the void-packages repository
https://github.com/pullmoll/void-packages libucontext
https://github.com/void-linux/void-packages/pull/21743
libucontext: switch upstream + update to 0.10
Upstream has updates to support `mips*` architectures.
This lets us build `ruby` and packages depending on it for `mips*` again.
A patch file from https://github.com/void-linux/void-packages/pull/21743.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libucontext-21743.patch --]
[-- Type: text/x-diff, Size: 2318 bytes --]
From f888ceb219bf2c55a24cfa20b34b68928132f81b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=BCrgen=20Buchm=C3=BCller?= <pullmoll@t-online.de>
Date: Fri, 8 May 2020 12:52:58 +0200
Subject: [PATCH 1/2] libucontext: switch upstream + update to 0.10
---
srcpkgs/libucontext/template | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/libucontext/template b/srcpkgs/libucontext/template
index b29d8aad105..fb466936985 100644
--- a/srcpkgs/libucontext/template
+++ b/srcpkgs/libucontext/template
@@ -1,19 +1,21 @@
# Template file for 'libucontext'
pkgname=libucontext
-version=0.9.0
+version=0.10
revision=1
+wrksrc="${pkgname}-${pkgname}-${version}"
archs="*-musl"
short_desc="Compatibility layer providing ucontext functions"
maintainer="Peter Bui <pbui@github.bx612.space>"
license="ISC"
-homepage="https://code.foxkit.us/adelie/libucontext"
-distfiles="https://distfiles.adelielinux.org/source/${pkgname}/${pkgname}-${version}.tar.xz"
-checksum=0d53a415a307ef175153bbe60a572c940a922cb736ce13530b666e7ec2795d68
+homepage="https://github.com/kaniini/libucontext"
+distfiles="https://github.com/kaniini/libucontext/archive/${pkgname}-${version}.tar.gz"
+checksum=e77dee222a31d6ad66c7668ceab197ac683349ab943f66cfe8c324324778ac9f
case "${XBPS_TARGET_MACHINE}" in
arm*) export LIBUCONTEXT_ARCH="arm";;
i686*) export LIBUCONTEXT_ARCH="x86";;
ppc64*) export LIBUCONTEXT_ARCH="ppc64";;
+mips*) export LIBUCONTEXT_ARCH="mips";;
*) export LIBUCONTEXT_ARCH="${XBPS_TARGET_MACHINE%%-musl}";;
esac
From c65e54cc46cebc7a9d5cd98fd303a1b8906649e2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=BCrgen=20Buchm=C3=BCller?= <pullmoll@t-online.de>
Date: Fri, 8 May 2020 12:56:42 +0200
Subject: [PATCH 2/2] ruby: libucontext support for mips*
---
srcpkgs/ruby/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/ruby/template b/srcpkgs/ruby/template
index 67bc2a1352a..7acbcbd6263 100644
--- a/srcpkgs/ruby/template
+++ b/srcpkgs/ruby/template
@@ -37,7 +37,7 @@ case "$XBPS_TARGET_MACHINE" in
ppc64*) # Default is ucontext on BE, but ppc64le really just means ELFv2
configure_args+=" --with-coroutine=ppc64le"
;;
- ppc-musl)
+ mips*|ppc-musl)
_need_libucontext=yes
makedepends+=" libucontext-devel"
configure_args+=" LIBS=-lucontext"
next prev parent reply other threads:[~2020-05-08 10:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 10:54 [PR PATCH] " pullmoll
2020-05-08 10:56 ` pullmoll [this message]
2020-05-08 11:07 ` [PR PATCH] [Updated] " pullmoll
2020-05-08 11:23 ` pullmoll
2020-05-08 14:12 ` pullmoll
2020-05-08 14:20 ` pbui
2020-05-08 14:26 ` [PR PATCH] [Updated] " pullmoll
2020-05-08 14:28 ` pullmoll
2020-05-08 15:14 ` q66
2020-05-08 16:46 ` [PR PATCH] [Updated] " pullmoll
2020-05-08 16:47 ` pullmoll
2020-05-08 16:48 ` pullmoll
2020-05-08 16:50 ` pullmoll
2020-05-08 21:08 ` [PR PATCH] [Merged]: " pullmoll
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=20200508105611.FoNPNT632ZLYCZFU6MqVg0RBVAHKEeLHAnpV-fLcka0@z \
--to=pullmoll@users.noreply.github.com \
--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).