From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] crystal: update to 0.31.1.
Date: Mon, 30 Sep 2019 22:27:08 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14858@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
There is a new pull request by gcat432 against master on the void-packages repository
https://github.com/gcat432/void-packages crystal-0.31.1
https://github.com/void-linux/void-packages/pull/14858
crystal: update to 0.31.1.
- Compilation was locally tested with both i686 and x86_64
- Package was locally installed on x86_64, `crystal` and `shards` work good
- Issue with multi-threading: it is not possible to compile programs with the `-Dpreview_mt` flag. As said in #14688 a patch to `gc` is required for them to work, and we will eventually not bump this package until a new release which will contain this new feature.
**Note to Crystal developers:** If you really want to enable green threads support in the `gc` package, please use [this patch](https://gist.github.com/gcat432/2f7f000624c9333483e2a5b9abfba146) and compile `gc` (I did it using `xbps-src` using the same revision and force reinstalled it: it works without issue). Good luck!
A patch file from https://github.com/void-linux/void-packages/pull/14858.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-crystal-0.31.1-14858.patch --]
[-- Type: text/x-diff, Size: 2194 bytes --]
From 36df6577a2c409f3b5305822b928e2ce307ef205 Mon Sep 17 00:00:00 2001
From: Gangsta Cat <grumpy@keemail.me>
Date: Mon, 30 Sep 2019 22:22:09 +0200
Subject: [PATCH] crystal: update to 0.31.1.
---
srcpkgs/crystal/template | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/crystal/template b/srcpkgs/crystal/template
index ef02626bc3c..2bb0db5dc81 100644
--- a/srcpkgs/crystal/template
+++ b/srcpkgs/crystal/template
@@ -1,10 +1,10 @@
# Template file for 'crystal'
pkgname=crystal
-version=0.31.0
+version=0.31.1
revision=1
archs="x86_64* i686* aarch64* arm*"
_shardsversion=0.9.0
-_bootstrapversion=0.31.0
+_bootstrapversion=0.31.1
_bootstraprevision=1
hostmakedepends="git llvm8"
makedepends="gc-devel libatomic_ops pcre-devel libevent-devel libyaml-devel
@@ -19,7 +19,7 @@ homepage="https://crystal-lang.org/"
distfiles="
https://github.com/crystal-lang/crystal/archive/${version}.tar.gz
https://github.com/crystal-lang/shards/archive/v${_shardsversion}.tar.gz"
-checksum="483ffcdce30b98f89b8c6cf6e48c62652cd0450205f609e04721a37997c32486
+checksum="b4a51164763b891572492e2445d3a69b462675184ea0ccf06fcc57a070f07b80
90f230c87cc7b94ca845e6fe34f2523edcadb562d715daaf98603edfa2a94d65"
nocross="FIXME: someone needs to sort out the llvm --cxxflags for cross building"
_crystalflags="--release --no-debug --progress"
@@ -32,11 +32,11 @@ if [ "$build_option_binary_bootstrap" ]; then
case "$XBPS_MACHINE" in
x86_64)
distfiles+=" https://github.com/crystal-lang/crystal/releases/download/${_bootstrapversion}/crystal-${_bootstrapversion}-${_bootstraprevision}-linux-x86_64.tar.gz"
- checksum+=" e0edff85da9375178f2e5c72845b6d3eb6abc1d9e32c9033451ae4c1fc0bf09a"
+ checksum+=" 308a5891322287852ba492e6e0dcc1484af361c189525349b6b98b531c551a65"
;;
i686)
distfiles+=" https://github.com/crystal-lang/crystal/releases/download/${_bootstrapversion}/crystal-${_bootstrapversion}-${_bootstraprevision}-linux-i686.tar.gz"
- checksum+=" a451e997378bc1230241b0e40023b8f0d754fd68943c5a8e77840d4fac0c5647"
+ checksum+=" 394bfe422bd2e74b6c5a99d31dcd873ec3f25c3f06834e1dd779efa2a36d3143"
;;
*)
broken="cannot be built on $XBPS_MACHINE"
next reply other threads:[~2019-09-30 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 20:27 voidlinux-github [this message]
2019-10-01 19:40 ` [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-14858@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).