From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH v2 5/7] gnu: colord: Add libcap input.
Date: Tue, 25 Aug 2015 17:03:38 +0200 [thread overview]
Message-ID: <87r3mrl8ad.fsf@gnu.org> (raw)
In-Reply-To: <343668288df3ea70e22d3aae3f28b63a3eeba95f.1440062095.git.wingo@pobox.com> (Andy Wingo's message of "Tue, 18 Aug 2015 11:54:13 +0200")
Andy Wingo <wingo@pobox.com> skribis:
> * gnu/packages/gnome.scm (colord): Add libcap as an input. I don't know why;
> I suspect something libtool-related with libelogind.la.
If libelogind.la has a -lcap without -L/...-libcap, then could you add a
phase there to do that instead? (For example the recipe for hwloc does
that.)
If it’s libelogind.pc that “Requires” libcap’s .pc, then the solution is
to propagate libcap from elogind.
Hope this makes sense!
Ludo’.
next prev parent reply other threads:[~2015-08-25 15:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 8:03 [PATCH v2 1/7] guix: git: Support shallow git clones if a tag is available Andy Wingo
2015-08-18 8:05 ` [PATCH v2 2/7] gnu: elogind: Update to version 219.5 Andy Wingo
2015-08-25 14:46 ` Ludovic Courtès
2015-08-18 8:22 ` [PATCH v2 3/7] gnu: Allow OS configurations to add PAM session modules Andy Wingo
2015-08-25 14:55 ` Ludovic Courtès
2015-08-25 16:00 ` Andy Wingo
2015-08-25 21:39 ` Ludovic Courtès
2015-08-26 7:21 ` Andy Wingo
2015-08-26 7:36 ` 宋文武
2015-08-28 9:04 ` Ludovic Courtès
2015-08-18 9:39 ` [PATCH v2 4/7] gnu: polkit: Use elogind for seat management Andy Wingo
2015-08-25 14:56 ` Ludovic Courtès
2015-08-25 16:00 ` Andy Wingo
2015-08-18 9:54 ` [PATCH v2 5/7] gnu: colord: Add libcap input Andy Wingo
2015-08-25 15:03 ` Ludovic Courtès [this message]
2015-08-25 16:01 ` Andy Wingo
2015-08-25 21:40 ` Ludovic Courtès
2015-08-18 9:56 ` [PATCH v2 6/7] gnu: Add elogind service Andy Wingo
2015-08-25 15:04 ` Ludovic Courtès
2015-08-18 9:57 ` [PATCH v2 7/7] gnu: Add polkit service Andy Wingo
2015-08-25 15:05 ` 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=87r3mrl8ad.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=wingo@pobox.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.