From: desertsagebrush <desertsagebrush@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] i3status-rust: update to 0.32.3
Date: Mon, 25 Dec 2023 23:03:24 +0100 [thread overview]
Message-ID: <20231225220324.tVfPDC8cv5T5iRjk4SsFuFKLU9MWdBT1GnMHx9lL2kM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47870@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
New review comment by desertsagebrush on void-packages repository
https://github.com/void-linux/void-packages/pull/47870#discussion_r1436158467
Comment:
Part of the problem is that there are few diagnostics coming out of `vtargetrun`; whenever there is an error (other than an error with args for qemu) it just pops up:
```
=> i3status-rust-0.32.3_1: running post_build ...
Finished release [optimized] target(s) in 0.09s
=> ERROR: i3status-rust-0.32.3_1: post_build: '"/usr/bin/qemu-${XBPS_TARGET_QEMU_MACHINE}-static" "$@"' exited with 1
=> ERROR: in vtargetrun() at common/build-helper/qemu.sh:10
=> ERROR: in post_build() at srcpkgs/i3status-rust/template:20
```
While I can manually poke the generated binary (and the command line I'm passing to it) for x86_64, the lack of diagnostics means that trying to make sure everything works for cross-compiling is a bit more challenging.
next prev parent reply other threads:[~2023-12-25 22:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 6:03 [PR PATCH] " desertsagebrush
2023-12-22 6:11 ` [PR PATCH] [Updated] " desertsagebrush
2023-12-22 18:22 ` desertsagebrush
2023-12-23 13:33 ` [PR REVIEW] " classabbyamp
2023-12-23 20:49 ` desertsagebrush
2023-12-23 20:52 ` desertsagebrush
2023-12-23 20:54 ` desertsagebrush
2023-12-23 21:09 ` classabbyamp
2023-12-23 21:13 ` classabbyamp
2023-12-25 21:57 ` desertsagebrush
2023-12-25 22:03 ` desertsagebrush [this message]
2023-12-25 22:09 ` desertsagebrush
2023-12-25 22:10 ` desertsagebrush
2023-12-25 22:15 ` desertsagebrush
2023-12-25 22:30 ` desertsagebrush
2023-12-25 22:34 ` desertsagebrush
2023-12-25 22:46 ` [PR PATCH] [Updated] " desertsagebrush
2023-12-25 22:48 ` desertsagebrush
2023-12-25 22:49 ` [PR REVIEW] " desertsagebrush
2023-12-25 22:51 ` desertsagebrush
2023-12-31 19:37 ` desertsagebrush
2024-01-07 4:56 ` [PR PATCH] [Updated] " classabbyamp
2024-01-07 4:57 ` classabbyamp
2024-01-07 4:57 ` classabbyamp
2024-01-07 5:14 ` [PR PATCH] [Merged]: " classabbyamp
2024-01-13 19:07 ` desertsagebrush
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=20231225220324.tVfPDC8cv5T5iRjk4SsFuFKLU9MWdBT1GnMHx9lL2kM@z \
--to=desertsagebrush@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).