all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: guix-devel@gnu.org
Subject: Re: gold linker and collect2: fatal error: cannot find 'ld'
Date: Tue, 19 Mar 2019 16:24:08 +0100	[thread overview]
Message-ID: <20190319152408.sw4f5omaljp7bef2@thebird.nl> (raw)
In-Reply-To: <20190318152849.n3jzwrbyfd7fd3db@thebird.nl>

No one suggestions? Should we disable gold?

On Mon, Mar 18, 2019 at 04:28:49PM +0100, Pjotr Prins wrote:
> On Sun, Mar 17, 2019 at 05:06:16PM +0100, Pjotr Prins wrote:
> > Unfortunately the runtime of compiled software fails because the rpath is
> > not updated either. So that requires adding in the RPATH explicitly on
> > the ldc command line. When I set the RPATH the runtime is fine. 
> 
> Reading up on the ld-wrapper code - that is exactly what happens. A
> gold-wrapper can do same.
> 
> I think, like with rustc, I need to wrap the ldc compiler build with
> ld-wrapper and the ldc tests with gold-wrapper (yet to be written).
> 
> gold does not honour LIBRARY_PATH so that means we'll have to use
> LD_LIBRARY_PATH or pass the lib path(s) on the command line. 
> 
> Does this make sense? If it does we can make an attempt.
> 
> Pj.
> 

  reply	other threads:[~2019-03-19 15:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-17 16:06 gold linker and collect2: fatal error: cannot find 'ld' Pjotr Prins
2019-03-18 15:28 ` Pjotr Prins
2019-03-19 15:24   ` Pjotr Prins [this message]
2019-03-27 17:15   ` Ludovic Courtès
2019-05-01  7:56     ` Pierre Neidhardt
2019-05-16  5:18       ` Pierre Neidhardt
2019-05-17 13:44         ` Pierre Neidhardt
2019-05-17 18:13           ` Pierre Neidhardt
2019-05-20 15:35             ` Ludovic Courtès
2019-05-20 16:06               ` Pierre Neidhardt
2019-05-25 16:35                 ` Pierre Neidhardt
2019-05-25 21:21                   ` Pjotr Prins

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=20190319152408.sw4f5omaljp7bef2@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=guix-devel@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.