From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: contour-0.4.0.6245
Date: Sun, 31 Dec 2023 08:07:54 +0100 [thread overview]
Message-ID: <20231231070754.YK65KZ8U5uEV5n5JruxfW_Q_-ggFB0FE4j1Tel19i9o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47845@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
New comment by 0x5c on void-packages repository
https://github.com/void-linux/void-packages/pull/47845#issuecomment-1864030201
Comment:
Inventory of failure:
- cross archs: build tool is compiled for target [libunicode & contour]
→ `build_helper=qemu` is made of :magic_wand: *Magic* :sparkles:
- ~~i686 (glibc)~~ 32bit archs: c++ intrinsics sadness [libunicode]
→ Upstream says it's not supported (yet), marking broken
- x86_64-musl (all-musl?): pthread sadness [contour]
→ in musl land, you don't get a thread name
- aarch64: ??? [contour]
→ `qt6-base qt6-tools` in hostmakedepends, duh
next prev parent reply other threads:[~2023-12-31 7:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 7:48 [PR PATCH] " 0x5c
2023-12-20 8:04 ` 0x5c
2023-12-20 8:09 ` [PR PATCH] [Updated] " 0x5c
2023-12-20 8:13 ` 0x5c
2023-12-20 8:16 ` 0x5c
2023-12-20 8:19 ` 0x5c
2023-12-20 8:20 ` 0x5c
2023-12-20 9:01 ` [PR PATCH] [Updated] " 0x5c
2023-12-20 9:03 ` 0x5c
2023-12-20 9:24 ` [PR PATCH] [Updated] " 0x5c
2023-12-20 10:14 ` 0x5c
2023-12-20 10:58 ` 0x5c
2023-12-20 10:58 ` 0x5c
2023-12-20 10:58 ` 0x5c
2023-12-31 7:04 ` [PR PATCH] [Updated] " 0x5c
2023-12-31 7:07 ` 0x5c [this message]
2024-01-01 5:16 ` 0x5c
2024-01-05 5:22 ` [PR REVIEW] " classabbyamp
2024-01-05 5:22 ` classabbyamp
2024-01-05 5:22 ` classabbyamp
2024-01-05 23:05 ` [PR PATCH] [Updated] " 0x5c
2024-01-06 1:32 ` [PR PATCH] [Merged]: " classabbyamp
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=20231231070754.YK65KZ8U5uEV5n5JruxfW_Q_-ggFB0FE4j1Tel19i9o@z \
--to=0x5c@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).