From: Goorzhel <Goorzhel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: ncgopher-0.4.0
Date: Wed, 03 Aug 2022 05:14:40 +0200 [thread overview]
Message-ID: <20220803031440.P17W6NzUbHv0DNCypEm_gbYZkX17yQKFLMVZ0Ht2WMg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38444@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
New comment by Goorzhel on void-packages repository
https://github.com/void-linux/void-packages/pull/38444#issuecomment-1203434730
Comment:
On my host:
```
❯ git config alias.b
rev-parse --abbrev-ref HEAD
❯ ./xbps-src -a aarch64 pkg $(git b)
<...>
--- stderr
thread 'main' panicked at '/builddir/ncgopher-0.4.0/target/aarch64-unknown-linux-gnu/release/build/ncurses-e718d8c075f3805b/out/chtype_size failed: Os { code: 8, kind: Uncategorized, message: "Exec format error" }', /host/cargo/registry/src/github.com-1ecc6299db9ec823/ncurses-5.101.0/build.rs:107:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
=> ERROR: ncgopher-0.4.0_1: do_build: '${make_cmd} build --
```
Let's hope CI behaves differently.
next prev parent reply other threads:[~2022-08-03 3:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 1:07 [PR PATCH] " Goorzhel
2022-08-03 1:09 ` [PR PATCH] [Updated] " Goorzhel
2022-08-03 2:11 ` [PR REVIEW] " classabbyamp
2022-08-03 3:13 ` [PR PATCH] [Updated] " Goorzhel
2022-08-03 3:14 ` Goorzhel [this message]
2022-08-03 3:14 ` Goorzhel
2022-08-03 3:17 ` classabbyamp
2022-08-03 3:38 ` Goorzhel
2022-08-03 3:45 ` [PR PATCH] [Updated] " Goorzhel
2022-11-02 2:14 ` github-actions
2022-11-02 2:36 ` classabbyamp
2022-11-02 15:11 ` [PR PATCH] [Updated] " Goorzhel
2023-02-02 2:01 ` github-actions
2023-02-07 2:02 ` [PR PATCH] [Closed]: " Goorzhel
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=20220803031440.P17W6NzUbHv0DNCypEm_gbYZkX17yQKFLMVZ0Ht2WMg@z \
--to=goorzhel@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).