From: ludo@gnu.org (Ludovic Courtès)
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: kde: Add kdelibs.
Date: Wed, 05 Nov 2014 21:15:46 +0100 [thread overview]
Message-ID: <87tx2d2ykt.fsf@gnu.org> (raw)
In-Reply-To: <CAKrPhPOs3DFJQvb8zZ4vSWvJ7-uW1o8k1XLB_YXbh-ZKsXDA0g@mail.gmail.com> (Federico Beffa's message of "Wed, 5 Nov 2014 20:50:30 +0100")
Federico Beffa <beffa@ieee.org> skribis:
> 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.
What build system does dconf use?
Usually there’s no problem for packages that use Libtool (it sets the
RUNPATH automatically), but there’s almost systematically a problem when
CMake is used (we may not be passing the right options or something, as
Andreas notes.)
Ludo’.
next prev parent reply other threads:[~2014-11-05 20:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 19:50 [PATCH] gnu: kde: Add kdelibs Federico Beffa
2014-11-05 20:15 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tx2d2ykt.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=beffa@ieee.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.