Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Rust 1.40
Date: Sat, 28 Dec 2019 13:49:03 +0100	[thread overview]
Message-ID: <20191228124903.MSd72XWjZQlfASQ-8LC99qMP1JEEG2pvdgI0w67Pm68@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17684@inbox.vuxu.org>

[-- 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 

  parent reply	other threads:[~2019-12-28 12:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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
2019-12-28 12:49 ` voidlinux-github [this message]
2019-12-28 22:17 ` [PR PATCH] [Updated] " voidlinux-github
2019-12-28 22:18 ` voidlinux-github
2019-12-28 22:28 ` voidlinux-github
2019-12-29 15:22 ` [PR PATCH] [Merged]: " 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=20191228124903.MSd72XWjZQlfASQ-8LC99qMP1JEEG2pvdgI0w67Pm68@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).