From: loreb <loreb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: List of broken native aarch64-musl builds
Date: Wed, 15 Jun 2022 14:25:14 +0200 [thread overview]
Message-ID: <20220615122514.JlyDZ0-JO0oQEFEA3vumJbt7prq1KlgmA8K2IqhIU0E@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37497@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1899 bytes --]
New comment by loreb on void-packages repository
https://github.com/void-linux/void-packages/issues/37497#issuecomment-1156406268
Comment:
Hyperrogue has a new version but xbps-src says "NO VERSION";
sticking
```
site=https://github.com/zenorogue/hyperrogue/releases/latest
# adapted from wine/update
pattern="v\K[^\d]*([\d]+\.[a-z0-9]+)"
```
into hyperrogue/update almost works (it's VERY quick&dirty), but anyway, the point is: does the latest version (12.0q) compile for you?
```
diff --git a/srcpkgs/hyperrogue/template b/srcpkgs/hyperrogue/template
index 7f0b8da575..1c54f9c34d 100644
--- a/srcpkgs/hyperrogue/template
+++ b/srcpkgs/hyperrogue/template
@@ -1,8 +1,8 @@
# Template file for 'hyperrogue'
pkgname=hyperrogue
-version=11.3f
+version=12.0q
revision=1
-build_style=gnu-configure
+build_style=gnu-makefile
hostmakedepends="autoconf automake"
makedepends="glew-devel libpng-devel SDL-devel SDL_gfx-devel SDL_mixer-devel
SDL_ttf-devel zlib-devel"
@@ -11,13 +11,13 @@ maintainer="B. Wilson <x@wilsonb.com>"
license="GPL-2.0-or-later, CC-BY-SA-4.0, CC-BY-SA-3.0, CC-BY-3.0, Public Domain"
homepage="https://www.roguetemple.com/z/hyper/"
distfiles="https://github.com/zenorogue/hyperrogue/archive/v${version}.tar.gz"
-checksum=5451b35860c940adc422d455e42d702a76eb6595450e92cb2c0e432cf77ddd9b
+checksum=6e81b79b3eb206e93d0893874322308e3edd24a1695ed1670dfed7088b27891a
nocross="Generates code from build output that must run on host"
# SDL_gfx-devel headers require that SDL.h be under the header search paths,
# which are not set correctly by upstream.
CXXFLAGS+=" -I/usr/include/SDL"
-pre_configure() {
- autoreconf -i
-}
+#pre_configure() {
+# autoreconf -i
+#}
```
(fails at make install - it's the bare minimum to make it compile (on my machine) and see if we are lucky and an upgrade is all it takes to compile on aarch64)
next prev parent reply other threads:[~2022-06-15 12:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 21:17 [ISSUE] " paper42
2022-06-11 7:27 ` classabbyamp
2022-06-11 15:56 ` classabbyamp
2022-06-14 14:40 ` loreb
2022-06-14 16:12 ` paper42
2022-06-15 10:03 ` loreb
2022-06-15 10:12 ` loreb
2022-06-15 12:15 ` leahneukirchen
2022-06-15 12:25 ` loreb [this message]
2022-06-15 13:11 ` leahneukirchen
2022-06-15 14:34 ` paper42
2022-06-15 14:48 ` leahneukirchen
2022-06-15 14:55 ` sgn
2022-06-15 15:04 ` classabbyamp
2022-06-15 15:22 ` paper42
2022-06-15 15:43 ` tornaria
2022-06-15 16:21 ` classabbyamp
2022-06-16 21:36 ` leahneukirchen
2022-06-17 21:49 ` paper42
2022-06-18 13:13 ` loreb
2022-06-20 18:39 ` classabbyamp
2022-06-23 4:16 ` ericonr
2022-06-24 20:49 ` paper42
2022-06-25 0:40 ` ericonr
2022-06-25 0:41 ` ericonr
2022-06-25 0:48 ` ericonr
2022-06-29 18:50 ` loreb
2022-07-02 7:58 ` sgn
2022-07-02 9:01 ` sgn
2022-07-05 11:22 ` paper42
2022-07-10 23:03 ` manfredu
2022-07-10 23:40 ` paper42
2022-07-11 5:51 ` manfredu
2022-07-12 8:18 ` manfredu
2022-10-11 2:14 ` github-actions
2022-12-07 16:45 ` dkwo
2023-03-09 15:52 ` dkwo
2023-07-23 14:37 ` dkwo
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=20220615122514.JlyDZ0-JO0oQEFEA3vumJbt7prq1KlgmA8K2IqhIU0E@z \
--to=loreb@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).