From: Samuel Fadel <samuel@nihil.ws>
To: 61145@debbugs.gnu.org
Cc: Samuel Fadel <samuel@nihil.ws>
Subject: [bug#61145] [PATCH] Added libcap to the native inputs of mako.
Date: Sun, 29 Jan 2023 12:15:22 +0100 [thread overview]
Message-ID: <20230129111521.24921-1-samuel@nihil.ws> (raw)
Hi Guix,
I have prepared this patch to fix the build of mako 1.7.1. Here is the failed build log:
http://ci.guix.gnu.org/build/370206/details
I'm not sure if this is the correct way to address this issue, but in my local tests it fixes the build.
Samuel
***
This allows pkg-config to detect libcap during the build of mako. This is used
by meson to generate cargs for basu (a dependency of mako), which in turn
needs libcap.
* gnu/packages/wm.scm (mako)[native-inputs]: Added libcap
---
gnu/packages/wm.scm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gnu/packages/wm.scm b/gnu/packages/wm.scm
index 2fd70af07f..f17bc0af3f 100644
--- a/gnu/packages/wm.scm
+++ b/gnu/packages/wm.scm
@@ -1858,7 +1858,7 @@ (define-public mako
(search-input-file inputs "bin/jq")
" "))))))))
(inputs (list basu cairo gdk-pixbuf jq pango wayland))
- (native-inputs (list pkg-config scdoc wayland-protocols))
+ (native-inputs (list libcap pkg-config scdoc wayland-protocols))
(home-page "https://wayland.emersion.fr/mako")
(synopsis "Lightweight Wayland notification daemon")
(description "Mako is a lightweight notification daemon for Wayland
--
2.39.1
next reply other threads:[~2023-01-29 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 11:15 Samuel Fadel [this message]
2023-01-31 1:18 ` [bug#61191] [PATCH] gnu: Fix missing libcap dependency for mako Csepp
2023-02-09 14:29 ` bug#61191: Mako build fixed Jelle Licht
2023-01-31 18:06 ` [bug#61145] make & libcap itd
2023-02-01 17:15 ` Josselin Poiret via Guix-patches via
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=20230129111521.24921-1-samuel@nihil.ws \
--to=samuel@nihil.ws \
--cc=61145@debbugs.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.