From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] nushell: update to 0.26.0
Date: Thu, 04 Feb 2021 06:47:10 +0100 [thread overview]
Message-ID: <20210204054710.UZeOZPELp6G_MUTa6HVlTONoLgQcalq-lJuSkA6NhOM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28341@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/28341#issuecomment-773047030
Comment:
If nushell uses libgit deep down, the `zlib-devel` dependency is required because it's building a vendored in copy of libgit2, since our local one doesn't fullfill its version requirements. Please use `libgit2-devel` as a dependency, since that will pull in `zlib-devel`, which will fix the build while they use the vendored code, and automatically pick up the local version once our libgit2 package is updated.
Regarding type errors, they probably picked up a crate which interfaces with some C library and are trying to interface with it using `i8` or `u8`, instead of using `libc::c_char` (or whatever that type is called). Since Rust is way too strict about signedness, this breaks the build. Chars have different standard signedness on x86 vs other platforms.
next prev parent reply other threads:[~2021-02-04 5:47 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 18:33 [PR PATCH] " FollieHiyuki
2021-01-30 18:34 ` FollieHiyuki
2021-01-30 18:37 ` [PR PATCH] [Updated] " FollieHiyuki
2021-01-30 18:40 ` FollieHiyuki
2021-01-30 18:44 ` FollieHiyuki
2021-01-30 18:45 ` FollieHiyuki
2021-01-30 18:47 ` FollieHiyuki
2021-01-30 19:29 ` [PR PATCH] [Updated] " FollieHiyuki
2021-01-30 19:58 ` FollieHiyuki
2021-01-31 0:33 ` [PR PATCH] [Updated] " FollieHiyuki
2021-02-04 5:40 ` ahesford
2021-02-04 5:45 ` ericonr
2021-02-04 5:47 ` ericonr [this message]
2021-02-04 6:35 ` FollieHiyuki
2021-02-04 6:55 ` [PR PATCH] [Updated] " FollieHiyuki
2021-02-04 6:58 ` FollieHiyuki
2021-02-04 8:15 ` [PR PATCH] [Updated] " FollieHiyuki
2021-02-06 5:40 ` ericonr
2021-02-06 6:42 ` [PR PATCH] [Updated] " FollieHiyuki
2021-02-06 6:47 ` FollieHiyuki
2021-02-06 6:50 ` FollieHiyuki
2021-02-06 6:54 ` FollieHiyuki
2021-02-06 7:01 ` FollieHiyuki
2021-02-06 7:02 ` FollieHiyuki
2021-02-06 7:10 ` FollieHiyuki
2021-02-14 21:26 ` ericonr
2021-02-14 23:17 ` [PR PATCH] [Updated] " FollieHiyuki
2021-02-15 18:40 ` FollieHiyuki
2021-02-15 18:53 ` ericonr
2021-02-16 6:27 ` [PR REVIEW] " ericonr
2021-02-16 6:27 ` ericonr
2021-02-16 6:27 ` ericonr
2021-02-16 11:33 ` [PR PATCH] [Updated] " FollieHiyuki
2021-02-16 11:38 ` [PR REVIEW] " FollieHiyuki
2021-02-16 11:41 ` FollieHiyuki
2021-02-16 11:42 ` FollieHiyuki
2021-02-16 17:43 ` [PR PATCH] [Updated] " FollieHiyuki
2021-02-16 17:45 ` FollieHiyuki
2021-02-16 17:56 ` [PR REVIEW] " FollieHiyuki
2021-02-16 18:11 ` [PR PATCH] [Merged]: " ericonr
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=20210204054710.UZeOZPELp6G_MUTa6HVlTONoLgQcalq-lJuSkA6NhOM@z \
--to=ericonr@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).