From: "Ludovic Courtès" <ludo@gnu.org>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: gold linker and collect2: fatal error: cannot find 'ld'
Date: Wed, 27 Mar 2019 18:15:26 +0100 [thread overview]
Message-ID: <87lg109r2p.fsf@gnu.org> (raw)
In-Reply-To: <20190318152849.n3jzwrbyfd7fd3db@thebird.nl> (Pjotr Prins's message of "Mon, 18 Mar 2019 16:28:49 +0100")
Hi Pjotr,
Pjotr Prins <pjotr.public12@thebird.nl> skribis:
> 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).
Indeed. We’d just need to add a parameter to ‘make-ld-wrapper’ so we
can specify the executable name, which would be “gold” instead of “ld”
in this case.
Would you like to give it a try?
> 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.
LIBRARY_PATH is honored by gcc, which “converts” it into a list of -L
flags for the linker, so no worries here.
HTH, and sorry for the delay!
Ludo’.
next prev parent reply other threads:[~2019-03-27 17:15 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
2019-03-27 17:15 ` Ludovic Courtès [this message]
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=87lg109r2p.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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.