From: Alexandros Theodotou <alex@zrythm.org>
To: 40197@debbugs.gnu.org
Subject: [bug#40197] [PATCH] gnu: sord: Add pcre to inputs.
Date: Mon, 23 Mar 2020 16:56:05 +0000 [thread overview]
Message-ID: <6ed9c333f5aa1fbb7d5d2f768d9babc223499e30.camel@zrythm.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 354 bytes --]
Hi,
Sord did not have the `sord_validate` binary (which is needed for
`lv2_validate` from the lv2 package to function properly).
I looked it up and apparently it needs pcre to build:
https://gitlab.com/drobilla/sord/-/blob/master/wscript#L211
I have verified that adding pcre as an input now produces sord_validate
in /bin.
Thanks,
Alex
[-- Attachment #1.2: 0001-gnu-sord-Add-pcre-to-inputs.patch --]
[-- Type: text/x-patch, Size: 839 bytes --]
From 3edad6b801d4328e0ebdf9a9244a00fcbd8fda70 Mon Sep 17 00:00:00 2001
From: Alexandros Theodotou <alex@zrythm.org>
Date: Mon, 23 Mar 2020 16:51:44 +0000
Subject: [PATCH] gnu: sord: Add pcre to inputs.
* gnu/packages/rdf.scm (sord): Add pcre needed for sord_validate
---
gnu/packages/rdf.scm | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gnu/packages/rdf.scm b/gnu/packages/rdf.scm
index b9abd37e40..15f8d64d43 100644
--- a/gnu/packages/rdf.scm
+++ b/gnu/packages/rdf.scm
@@ -319,6 +319,8 @@ ideal (e.g. in LV2 implementations or embedded applications).")
(string-append "-Wl,-rpath="
(assoc-ref outputs "out") "/lib"))
#t)))))
+ (inputs
+ `(("pcre" ,pcre)))
(native-inputs
`(("pkg-config" ,pkg-config)))
(propagated-inputs
--
2.25.1
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-03-23 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 16:56 Alexandros Theodotou [this message]
2020-03-23 19:54 ` [bug#40197] [PATCH] gnu: sord: Add pcre to inputs Mathieu Othacehe
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=6ed9c333f5aa1fbb7d5d2f768d9babc223499e30.camel@zrythm.org \
--to=alex@zrythm.org \
--cc=40197@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.