From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New Packages: sequoia cli utilities
Date: Sat, 14 May 2022 11:43:30 +0200 [thread overview]
Message-ID: <20220514094330.PlbZ7FbBMsnuybJgY_9NoGpJ1Pz2Zyl-54htVnzb1Gg@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: 1213 bytes --]
New comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/pull/32480#issuecomment-1126681248
Comment:
So, I've done some digging, and I'd like to just outright disable armv7l and musl targets for now.
In the case of musl, this is part of time64, the migration to using 64 bit integers for time on 32 bit systems. Rust added a deprecation warning for that, and this warning is currently breaking the build here. There's stuff happening in that area, but it's a bigger problem that's not really related to sequoia directly, so not really something that can be addressed in this PR.
As for armv7l: A crypto library used by sequoia, nettle, for some reason fails to have it's rust bindings compiled for armv7l, because `cross-armv7l-linux-gnueabihf-libc` doesn't provide `gnu/stubs-soft.h`, which is referenced by `gnu/stubs.h`, based on some ifdef magic. I don't get where this is going wrong, but I don't understand enough of the arkane ifdef and crosscompiling magic to dig through this. If anyone else wants to, I'd be more than happy, but I won't invest any more time in trying to figure out why `stubs-soft.h` would even be considered required on a `hf` target.
next prev parent reply other threads:[~2022-05-14 9:43 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 [this message]
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
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=20220514094330.PlbZ7FbBMsnuybJgY_9NoGpJ1Pz2Zyl-54htVnzb1Gg@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).