From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New Packages: sequoia cli utilities
Date: Wed, 10 Aug 2022 01:19:26 +0200 [thread overview]
Message-ID: <20220809231926.XseG43FhdI5wP-Vy-W1FM-3xA76l4r0iNMREmK2hytY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32480@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
New comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/pull/32480#issuecomment-1209986035
Comment:
TL;DW of the problem here: `sq` depends on nettle-sys for both host (in build.rs) as well as target (for the application itself). Getting `bindgen` to work correctly for both host and target in our cross compilation setup is *super* tricky, and I've sunken many, many hours into it without getting anywhere so far. For most architectures it works anyway, but on armv*l it breaks due to some import trying to get in `/usr/include/gnu/stubs-soft.h` even though they are hard-float architectures, meaning that the file just doesn't exist.
I've tried patching out the requirement for nettle-sys in sq's build.rs script, but that ended up being a way bigger challenge than anticipated, and I'd prefer to just mark this as nocross for the affected architectures for now. If someone could validate that it works on those architectures at all, I'd be very happy about it as I currently don't have any armv7l device anymore to test on, but I suspect that it just works on those.
next prev parent reply other threads:[~2022-08-09 23:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 14:11 [PR PATCH] " jcgruenhage
2021-08-13 16:13 ` [PR PATCH] [Updated] " jcgruenhage
2021-08-13 16:16 ` jcgruenhage
2021-08-13 16:55 ` jcgruenhage
2022-01-15 15:32 ` jcgruenhage
2022-02-08 14:42 ` jcgruenhage
2022-02-08 22:14 ` jcgruenhage
2022-02-21 5:00 ` jcgruenhage
2022-02-26 18:30 ` jcgruenhage
2022-04-09 14:54 ` jcgruenhage
2022-04-09 15:18 ` [PR REVIEW] " classabbyamp
2022-04-09 15:28 ` jcgruenhage
2022-04-09 16:05 ` jcgruenhage
2022-05-14 9:43 ` jcgruenhage
2022-05-14 9:46 ` [PR PATCH] [Updated] " jcgruenhage
2022-05-15 21:32 ` ericonr
2022-05-15 22:43 ` classabbyamp
2022-06-02 9:12 ` [PR PATCH] [Updated] " jcgruenhage
2022-06-02 9:46 ` jcgruenhage
2022-06-03 9:54 ` jcgruenhage
2022-06-14 12:10 ` [PR PATCH] [Updated] " jcgruenhage
2022-06-14 12:47 ` jcgruenhage
2022-06-14 14:10 ` jcgruenhage
2022-06-14 14:20 ` jcgruenhage
2022-08-01 14:57 ` [PR PATCH] [Updated] " jcgruenhage
2022-08-07 16:38 ` jcgruenhage
2022-08-08 20:32 ` jcgruenhage
2022-08-08 21:16 ` [PR REVIEW] " classabbyamp
2022-08-08 21:16 ` classabbyamp
2022-08-09 8:54 ` [PR PATCH] [Updated] " jcgruenhage
2022-08-09 22:24 ` jcgruenhage
2022-08-09 23:19 ` jcgruenhage [this message]
2022-08-09 23:25 ` jcgruenhage
2022-08-12 6:41 ` [PR REVIEW] " ericonr
2022-08-12 7:42 ` jcgruenhage
2022-08-12 17:45 ` ahesford
2022-09-21 10:23 ` [PR PATCH] [Merged]: " ahesford
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=20220809231926.XseG43FhdI5wP-Vy-W1FM-3xA76l4r0iNMREmK2hytY@z \
--to=jcgruenhage@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).