unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Matthew Kraai <kraai@ftbfs.org>
Cc: guix-devel@gnu.org
Subject: Re: RUNPATH problem building Rust 1.40.0
Date: Sun, 28 Jun 2020 23:04:58 +0200	[thread overview]
Message-ID: <871rlygav9.fsf@gnu.org> (raw)
In-Reply-To: <20200628161212.GA9864@inspiron-3147> (Matthew Kraai's message of "Sun, 28 Jun 2020 09:12:12 -0700")

Hi,

Matthew Kraai <kraai@ftbfs.org> skribis:

> It currently fails to build with the following error:
>
> /gnu/store/j4zssa8y397q5l2hgkj5svcnj8dlgg32-rust-1.40.0/lib/rustlib/x86_64-unknown-linux-gnu/codegen-backends/librustc_codegen_llvm-llvm.so: error: depends on 'librustc_driver-1040000d6b8afc7f.so', which cannot be found in RUNPATH ("/gnu/store/j4zssa8y397q5l2hgkj5svcnj8dlgg32-rust-1.40.0/lib/rustlib/x86_64-unknown-linux-gnu/codegen-backends/../lib" "/gnu/store/sqpf340l6nnjw33395kmjv97vm8bp8pv-llvm-8.0.0/lib" "/gnu/store/01b4w3m6mp55y531kyi1g8shh722kwqm-gcc-7.5.0-lib/lib/gcc/x86_64-unknown-linux-gnu/7.5.0/../../.." "/gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib")
>
> librustc_driver-1040000d6b8afc7f.so is in
> /gnu/store/j4zssa8y397q5l2hgkj5svcnj8dlgg32-rust-1.40.0/lib, which is
> not in the RUNPATH.  Does anyone know how I should resolve this?

I don’t know Rust, but perhaps you could move
librustc_driver-1040000d6b8afc7f.so to
/gnu/store/j4zssa8y397q5l2hgkj5svcnj8dlgg32-rust-1.40.0/lib/rustlib/x86_64-unknown-linux-gnu/codegen-backends/../lib
since that one is in the RUNPATH.

Would be good to check with Rust-savvy people though.  :-)

Ludo’.


  reply	other threads:[~2020-06-28 21:05 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 [this message]
2020-07-01  6:15   ` John Soo

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=871rlygav9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=kraai@ftbfs.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).