From: kotajacob <kotajacob@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: hut-0.1.0
Date: Sun, 17 Apr 2022 00:43:39 +0200 [thread overview]
Message-ID: <20220416224339.zI9W5NJ6B72OUzt7b_FKfoqWArgIGlA-GL77u_U_2c4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36716@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2013 bytes --]
New comment by kotajacob on void-packages repository
https://github.com/void-linux/void-packages/pull/36716#issuecomment-1100765735
Comment:
The thing causing the build to fail on arm is generating shell completions. The `hut` package doesn't ship with completion scripts; you're meant to run `hut completion bash > hut.bash` to generate the script. There are two issues with this:
1. It seems like you need to set `build_helper=qemu` and run `hut` with `vtargetrun` in the post install stage rather than trying to run hut itself normally. Otherwise I don't think crosscompiles will work.
2. On arm (or maybe just crossbuilds in general) it seems like the binary for hut is not located in `$GOPATH/bin/hut` after compiling, but instead in `$GOPATH/bin/linux_arm64/hut`.
Number 1 seems to work fine with `vtargetrun`, but for number 2 I'm not sure the best way to handle this. I was thinking I could do something like `hutbin=$(find $GOPATH/bin -type f)` to get the `hut` binary path, but that throws a weird error message:
```
=> hut-0.1.0_1: running pre-install hook: 98-fixup-gir-path ...
ln: /destdir/aarch64-linux-gnu/hut-0.1.0/usr/aarch64-linux-gnu/usr/..: cannot overwrite directory
=> ERROR: hut-0.1.0_1: pre-install_98-fixup-gir-path: 'ln -sf ".." "${PKGDESTDIR}/usr/${XBPS_CROSS_TRIPLET}/usr"' exited with 1
=> ERROR: in hook() at common/hooks/pre-install/98-fixup-gir-path.sh:9
=> ERROR: in run_func() at common/xbps-src/shutils/common.sh:21
=> ERROR: in run_pkg_hooks() at common/xbps-src/shutils/common.sh:245
=> ERROR: in run_step() at common/xbps-src/shutils/common.sh:43
=> ERROR: in main() at common/xbps-src/libexec/xbps-src-doinstall.sh:37
```
Another option would be a switch statement for the arm architectures, but both of these seem hacky and not ideal. Maybe there's a simple environment variable that points to the binary you just installed or something? Will look into this further when I get some more time. Just wanted to update with the current progress.
next prev parent reply other threads:[~2022-04-16 22:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 3:57 [PR PATCH] " kotajacob
2022-04-16 3:58 ` the-maldridge
2022-04-16 4:04 ` [PR REVIEW] " classabbyamp
2022-04-16 4:29 ` kotajacob
2022-04-16 22:43 ` kotajacob [this message]
2022-04-16 23:33 ` classabbyamp
2022-04-16 23:37 ` classabbyamp
2022-04-17 1:02 ` [PR PATCH] [Updated] " kotajacob
2022-04-17 1:05 ` kotajacob
2022-07-01 6:03 ` [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=20220416224339.zI9W5NJ6B72OUzt7b_FKfoqWArgIGlA-GL77u_U_2c4@z \
--to=kotajacob@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).