* Re: Rust 1.40
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17684@inbox.vuxu.org>
@ 2019-12-28 12:01 ` voidlinux-github
2019-12-28 12:47 ` voidlinux-github
` (3 subsequent siblings)
4 siblings, 0 replies; 5+ messages in thread
From: voidlinux-github @ 2019-12-28 12:01 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 278 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/17684#issuecomment-569410588
Comment:
FWIW I could just now cross build rust for `armv7l-musl` using rust for `x86_64` without issues. Trying with rust for `x86_64-musl` now.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Rust 1.40
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17684@inbox.vuxu.org>
` (3 preceding siblings ...)
2019-12-28 22:18 ` voidlinux-github
@ 2019-12-28 22:28 ` voidlinux-github
4 siblings, 0 replies; 5+ messages in thread
From: voidlinux-github @ 2019-12-28 22:28 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 265 bytes --]
New comment by jnbr on void-packages repository
https://github.com/void-linux/void-packages/pull/17684#issuecomment-569455917
Comment:
Yes, musl builds are fine now, already tested this. Currently running glibc builds to make sure it doesn't break anything else.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Rust 1.40
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17684@inbox.vuxu.org>
` (2 preceding siblings ...)
2019-12-28 12:49 ` voidlinux-github
@ 2019-12-28 22:18 ` voidlinux-github
2019-12-28 22:28 ` voidlinux-github
4 siblings, 0 replies; 5+ messages in thread
From: voidlinux-github @ 2019-12-28 22:18 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 212 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/pull/17684#issuecomment-569455349
Comment:
added @jnbr's cargo patch to fix crossbuilds
@jnbr can you re-test this?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Rust 1.40
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17684@inbox.vuxu.org>
2019-12-28 12:01 ` Rust 1.40 voidlinux-github
2019-12-28 12:47 ` voidlinux-github
@ 2019-12-28 12:49 ` voidlinux-github
2019-12-28 22:18 ` voidlinux-github
2019-12-28 22:28 ` voidlinux-github
4 siblings, 0 replies; 5+ messages in thread
From: voidlinux-github @ 2019-12-28 12:49 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 661 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/pull/17684#issuecomment-569414066
Comment:
We figured it out yesterday, there is a regression in cargo that results in libraries from cross sysroot leaking into host, particularly libgcc_s; that results in certain configs breaking, e.g. aarch64-musl on x86_64-musl, with errors from host dynamic linker such as "unsupported relocation <N>" where N is some aarch64 reloc number... We will probably revert the rev in cargo locally
Rust builds fine as does the new cargo but trying to cross compile using this new cargo will result in the compiler failing to execute
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Rust 1.40
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17684@inbox.vuxu.org>
2019-12-28 12:01 ` Rust 1.40 voidlinux-github
@ 2019-12-28 12:47 ` voidlinux-github
2019-12-28 12:49 ` voidlinux-github
` (2 subsequent siblings)
4 siblings, 0 replies; 5+ messages in thread
From: voidlinux-github @ 2019-12-28 12:47 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 522 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/pull/17684#issuecomment-569414066
Comment:
We figured it out yesterday, there is a regression in cargo that results in libraries from cross sysroot leaking into host, particularly libgcc_s; that results in certain configs breaking, e.g. aarch64-musl on x86_64-musl, with errors from host dynamic linker such as "unsupported relocation <N>" where N is some aarch64 reloc number... We will probably revert the rev in cargo locally
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2019-12-28 22:28 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17684@inbox.vuxu.org>
2019-12-28 12:01 ` Rust 1.40 voidlinux-github
2019-12-28 12:47 ` voidlinux-github
2019-12-28 12:49 ` voidlinux-github
2019-12-28 22:18 ` voidlinux-github
2019-12-28 22:28 ` voidlinux-github
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).