From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add GCC front ends for Fortran, Go, Objective C, and Objective C++.
Date: Fri, 01 Nov 2013 23:41:38 +0100 [thread overview]
Message-ID: <87r4az68yl.fsf@gnu.org> (raw)
In-Reply-To: <87habvq1lo.fsf@karetnikov.org> (Nikita Karetnikov's message of "Sat, 02 Nov 2013 01:00:19 +0400")
Nikita Karetnikov <nikita@karetnikov.org> skribis:
>> ‘ld-wrapper’ is a wrapper around the linker that adds a -rpath argument
>> for each -l argument (see the top of ld-wrapper.scm), such that all the
>> needed libraries are in the resulting binary’s RUNPATH.
>
> Could you show how it helps to avoid the need to set environment
> variables?
In the general case, you wouldn’t want to type:
export LD_LIBRARY_PATH=/nix/store/foo:/nix/store/bar:...
More importantly, you could easily get it wrong, leading to crashes or
random behavior.
Setting RUNPATH at build time allows us to live our computing life in
peace and harmony.
HTH. :-)
Ludo’.
prev parent reply other threads:[~2013-11-01 22:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 2:59 GFortran can’t find system headers Nikita Karetnikov
2013-10-15 20:17 ` Ludovic Courtès
2013-10-17 12:59 ` Nikita Karetnikov
2013-10-17 15:29 ` Ludovic Courtès
2013-10-19 8:58 ` GCC front-ends (was: GFortran can’t find system headers) Nikita Karetnikov
2013-10-26 20:08 ` GCC front-ends Ludovic Courtès
2013-10-27 10:39 ` Andreas Enge
2013-10-28 13:07 ` Ludovic Courtès
2013-10-29 8:39 ` Andreas Enge
2013-10-29 10:32 ` Ludovic Courtès
2013-10-28 23:23 ` Nikita Karetnikov
2013-10-28 23:23 ` Ludovic Courtès
2013-10-28 23:38 ` Nikita Karetnikov
2013-10-31 20:13 ` [PATCH] gnu: Add GCC front ends for Fortran, Go, Objective C, and Objective C++ Nikita Karetnikov
2013-10-31 22:19 ` Ludovic Courtès
2013-11-01 21:00 ` Nikita Karetnikov
2013-11-01 22:41 ` Ludovic Courtès [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r4az68yl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=nikita@karetnikov.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.