all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Phase `validate-runpath' fails: lib not in RUNPATH
Date: Sun, 06 Nov 2016 20:28:20 +0100	[thread overview]
Message-ID: <87twbk8l2j.fsf@elephly.net> (raw)
In-Reply-To: <10612b67-4c72-1178-46a8-3a79572f3cde@crazy-compilers.com>


Hartmut Goebel <h.goebel@crazy-compilers.com> writes:

> I'm trying to build thunderbird ATM, modelled after the build for icecat.
>
> Phase `validate-runpath' fails with errors like this:
>
>     /gnu/store/…-thunderbird-45.4.0/lib/firefox-45.4.1/browser/components/libbrowsercomps.so:
>     error: depends on 'libplds4.so', which cannot be found in RUNPATH
>
>     /gnu/store/…-thunderbird-45.4.0/lib/firefox-devel-45.4.1/sdk/lib/libxul.so:
>     error: depends on 'libnspr4.so', which cannot be found in RUNPATH
>
> Any hint what this can be caused by?

This happens when libraries are referenced that are not in the default
library location of this package’s output directory.

In the package for R we have a similar situation and fix it by passing
these make flags:

       #:make-flags
       (list (string-append "LDFLAGS=-Wl,-rpath="
                            (assoc-ref %outputs "out")
                            "/lib/R/lib"))

This adds the “/lib/R/lib” directory to the RUNPATH, so that references
to these libraries can be properly embedded.

~~ Ricardo

  reply	other threads:[~2016-11-06 19:28 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 [this message]
2016-11-06 19:52   ` Hartmut Goebel
2016-11-06 20:34     ` Danny Milosavljevic
2016-11-07  3:21       ` Chris Marusich
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=87twbk8l2j.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    /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.