From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: rust: update to 1.38.0, cargo: update to 0.39.0
Date: Mon, 07 Oct 2019 18:26:02 +0200 [thread overview]
Message-ID: <20191007162602.JjlXPePNcIGMGtz2H8Z959AvRNoEj81vuC_BFgLr4PM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15178@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1534 bytes --]
There's a merged pull request on the void-packages repository
rust: update to 1.38.0, cargo: update to 0.39.0
https://github.com/void-linux/void-packages/pull/15178
Description:
Updated ppc distfiles already at https://repo.voidlinux-ppc.org/distfiles/ and ~~pending @Gottox merge~~mirrored into `alpha.de.repo.voidlinux.org`.
This also sets rust as nocross for now, to give native builders time to build first.
The 32-bit PowerPC (glibc) distfiles are custom for this release (and at least until the fixes have made it upstream) as there are ABI violation bugs that we are currently patching, which also break bootstrap (a patched compiler is necessary to build the compiler with the patches).
We're sticking with LLVM8 for now, as my testing with LLVM9 has revealed that some targets (at very least 32-bit ppc) generate broken executables with LLVM9. This cannot be conditionalized as Rust is an everything-crosscompiler. We can switch to LLVM9 once it's confirmed working (I raised it with the relevant people) - the bootstrap snapshots are made with static llvm so a switch should be fairly seamless with no bootstrap rebuilds.
This also updates cargo to 0.39 and deals with the libgit2 API/ABI breakage, in a kinda ugly (well, it is Rust...) but for now satisfactory way.
As far as I'm concerned, this should be ready to go, but testing pending for at least:
- [ ] x86_64
- [ ] x86_64-musl
- [ ] aarch64
- [ ] armv7l
Hopefully the current llvm8/9 merge fallout will be done by that time... :P
@jnbr
prev parent reply other threads:[~2019-10-07 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 14:49 [PR PATCH] " voidlinux-github
2019-10-07 5:29 ` voidlinux-github
2019-10-07 16:26 ` voidlinux-github [this message]
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=20191007162602.JjlXPePNcIGMGtz2H8Z959AvRNoEj81vuC_BFgLr4PM@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).