From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [FTBFS] cargo for x86_64-musl
Date: Sat, 01 Jun 2019 13:41:38 +0200 [thread overview]
Message-ID: <20190601114138.El-4o-0atIahTbnA39elTGq-uBciBd1vWKFX1fGzp48@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12058@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/12058#issuecomment-497937635
Comment:
Now trying to build rust for x86_64-musl with this patch:
```
--- rustc-1.35.0-src/vendor/libc/src/unix/notbsd/linux/mod.rs 2019-05-20 15:47:24.000000000 +0200
+++ rustc-1.35.0-src/vendor/libc/src/unix/notbsd/linux/mod.rs 2019-06-01 12:57:27.526582596 +0200
@@ -3,7 +3,7 @@
pub type useconds_t = u32;
pub type dev_t = u64;
pub type socklen_t = u32;
-pub type pthread_t = c_ulong;
+pub type pthread_t = u64;
pub type mode_t = u32;
pub type ino64_t = u64;
pub type off64_t = i64;
```
and see if that fixes building cargo.
I have no experience with rust and cargo so this patch may be plain stupid.
next prev parent reply other threads:[~2019-06-01 11:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 16:49 [ISSUE] " voidlinux-github
2019-06-01 11:41 ` voidlinux-github [this message]
2019-06-01 12:33 ` voidlinux-github
2019-06-01 13:04 ` voidlinux-github
2019-06-01 13:14 ` voidlinux-github
2019-06-01 13:14 ` voidlinux-github
2019-06-01 14:32 ` voidlinux-github
2019-06-02 23:20 ` voidlinux-github
2019-06-03 13:38 ` voidlinux-github
2019-06-03 13:38 ` [ISSUE] [CLOSED] " voidlinux-github
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=20190601114138.El-4o-0atIahTbnA39elTGq-uBciBd1vWKFX1fGzp48@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).