From: Federico Beffa <beffa@ieee.org>
To: andreas@enge.fr, Guix-devel <guix-devel@gnu.org>,
"Ludovic Courtès" <ludo@gnu.org>
Subject: Re: [PATCH] gnu: kde: Add kdelibs.
Date: Wed, 5 Nov 2014 20:50:30 +0100 [thread overview]
Message-ID: <CAKrPhPOs3DFJQvb8zZ4vSWvJ7-uW1o8k1XLB_YXbh-ZKsXDA0g@mail.gmail.com> (raw)
Andreas Enge <andreas@enge.fr> writes:
> As usual, the libraries and binaries are not explicitly linked with the
> libraries they depend on. So in a context where the input libraries are not
> in /usr/lib, executing binaries fails.
>
> In my private branch I also tried to compile a few KDE packages. The same
> problem everywhere: Unless I set an LD_LIBRARY_PATH, they do not find the
> necessary KDE and Qt libraries. I think we need a more general solution,
> as also witnessed by this:
I'm working on dconf and I had the same problem: the produced binaries
like dconf-edit, but even shared libraries produced by the build would
not find their own companions. Initially I did set LD_LIBRARY_PATH to
resolve the problem. However, after setting
#:configure-flags
;; Set the correct RUNPATH in binaries.
(list (string-append "LDFLAGS=-Wl,-rpath="
(assoc-ref %outputs "out") "/lib"))
at build time, everything was working fine without having to set
LD_LIBRARY_PATH. That is not in dconf and not in packages build against
dconf's libraries.
Regards,
Fede
next reply other threads:[~2014-11-05 19:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 19:50 Federico Beffa [this message]
2014-11-05 20:15 ` [PATCH] gnu: kde: Add kdelibs Ludovic Courtès
2014-11-05 20:28 ` Eric Bavier
2014-11-05 21:00 ` Federico Beffa
2014-11-05 21:18 ` Andreas Enge
2014-11-05 23:20 ` Andreas Enge
2014-11-06 11:46 ` Ludovic Courtès
2014-11-06 22:37 ` Andreas Enge
2014-11-06 22:54 ` Andreas Enge
2014-11-06 23:12 ` Andreas Enge
2014-11-06 23:09 ` Eric Bavier
2014-11-06 23:24 ` Andreas Enge
2014-11-07 9:20 ` Ludovic Courtès
2014-11-07 14:51 ` Andreas Enge
2014-11-07 14:59 ` 宋文武
[not found] <641d5f5d.31e3.14aaea456bc.Coremail.iyzsong@163.com>
2015-01-03 7:20 ` 宋文武
2015-01-03 11:06 ` Andreas Enge
2015-01-04 21:29 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2014-11-04 21:37 Andreas Enge
2014-11-05 13:18 ` Ludovic Courtès
2014-11-05 13:49 ` 宋文武
2014-11-05 19:22 ` Andreas Enge
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKrPhPOs3DFJQvb8zZ4vSWvJ7-uW1o8k1XLB_YXbh-ZKsXDA0g@mail.gmail.com \
--to=beffa@ieee.org \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).