all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Phase `validate-runpath' fails: lib not in RUNPATH
Date: Sun, 6 Nov 2016 20:52:20 +0100	[thread overview]
Message-ID: <d7652b40-56d8-63be-e600-58c2d0209d41@crazy-compilers.com> (raw)
In-Reply-To: <87twbk8l2j.fsf@elephly.net>

Am 06.11.2016 um 20:28 schrieb Ricardo Wurmus:
> Hartmut Goebel <h.goebel@crazy-compilers.com> writes:
>
>>     /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
>        #: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.

Thanks for this tip. I'm cuprous, though . Both "libplds4.so" and
"libnspr4.so" are part of "nspr" which is specified as input.

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

  reply	other threads:[~2016-11-06 19:52 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 [this message]
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=d7652b40-56d8-63be-e600-58c2d0209d41@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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.