From: Chris Marusich <cmmarusich@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Phase `validate-runpath' fails: lib not in RUNPATH
Date: Sun, 06 Nov 2016 19:21:08 -0800 [thread overview]
Message-ID: <87y40wht5n.fsf@gmail.com> (raw)
In-Reply-To: <20161106213439.6010e115@scratchpost.org> (Danny Milosavljevic's message of "Sun, 6 Nov 2016 21:34:39 +0100")
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
Danny Milosavljevic <dannym@scratchpost.org> writes:
> On Sun, 6 Nov 2016 20:52:20 +0100
> Hartmut Goebel <h.goebel@crazy-compilers.com> wrote:
>> Thanks for this tip. I'm cuprous, though . Both "libplds4.so" and
>> "libnspr4.so" are part of "nspr" which is specified as input.
>
> Yes, but will the linker embed the full path to libnspr4.so into the
> executable (or in your case shared library) it builds for thunderbird?
> If not, ld.so would pick up a random package at runtime (one it just
> happens to find in the library search path) - something we don't want.
>
> What the ld option "rpath" does is embed the full path to libnspr4.so
> into the executable (or in this case shared object) it builds. In this
> way it will pick exactly this libnspr4.so library or fail at startup.
I thought the default gnu build system arranges for the rpath to be set
correctly in the executables? Why would we need to add code here to do
that for this one package? I thought it would happen automatically.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-11-07 3:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 18:11 Phase `validate-runpath' fails: lib not in RUNPATH Hartmut Goebel
2016-11-06 19:28 ` Ricardo Wurmus
2016-11-06 19:52 ` Hartmut Goebel
2016-11-06 20:34 ` Danny Milosavljevic
2016-11-07 3:21 ` Chris Marusich [this message]
2016-11-07 9:03 ` Ludovic Courtès
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=87y40wht5n.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=dannym@scratchpost.org \
--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.