unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Soo <jsoo1@asu.edu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, Matthew Kraai <kraai@ftbfs.org>
Subject: Re: RUNPATH problem building Rust 1.40.0
Date: Tue, 30 Jun 2020 23:15:54 -0700	[thread overview]
Message-ID: <50AD21BD-65B0-4215-A526-7D891E4F0E1B@asu.edu> (raw)
In-Reply-To: <871rlygav9.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 175 bytes --]

Hi Matthew and Ludo,

I’ve been using the rust versions (up to 1.44) from this patch set without issue:

http://issues.guix.gnu.org/40957

Hope that helps,

John


[-- Attachment #2: Type: text/html, Size: 551 bytes --]

      reply	other threads:[~2020-07-01  6:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-28 16:12 RUNPATH problem building Rust 1.40.0 Matthew Kraai
2020-06-28 21:04 ` Ludovic Courtès
2020-07-01  6:15   ` John Soo [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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50AD21BD-65B0-4215-A526-7D891E4F0E1B@asu.edu \
    --to=jsoo1@asu.edu \
    --cc=guix-devel@gnu.org \
    --cc=kraai@ftbfs.org \
    --cc=ludo@gnu.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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).