From: Sergei Trofimovich <slyfox@inbox.ru>
To: 26805@debbugs.gnu.org
Subject: bug#26805: [PATCH] gs-fonts: add missing podule imports
Date: Sat, 6 May 2017 16:40:35 +0100 [thread overview]
Message-ID: <20170506154035.23664-1-slyfox@inbox.ru> (raw)
On code-updates branch 'gs-fonts' build fails as:
ice-9/psyntax.scm:1534:32: In procedure expand-macro:
ice-9/psyntax.scm:1534:32: Syntax error:
...-gs-fonts-8.11-guile-builder:1:2300: source expression failed to match
any pattern in form (%modify-phases phases* (delete (quote configure)))
builder for `/gnu/store/...-gs-fonts-8.11.drv' failed with exit code 1
* gnu/packages/ghostscript.scm (gs-fonts): add missing modules to
%modify-phases call: gnu-build-system, utils, srfi-1
Signed-off-by: Sergei Trofimovich <slyfox@inbox.ru>
---
gnu/packages/ghostscript.scm | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/gnu/packages/ghostscript.scm b/gnu/packages/ghostscript.scm
index 076046e72..33b8f51b6 100644
--- a/gnu/packages/ghostscript.scm
+++ b/gnu/packages/ghostscript.scm
@@ -273,6 +273,10 @@ architecture.")
(build-system gnu-build-system)
(arguments
`(#:tests? #f ; nothing to check, just files to copy
+
+ #:modules ((guix build gnu-build-system)
+ (guix build utils)
+ (srfi srfi-1))
#:phases
(modify-phases %standard-phases
(delete 'configure)
--
2.12.2
next reply other threads:[~2017-05-06 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-06 15:40 Sergei Trofimovich [this message]
2017-05-07 19:06 ` bug#26805: [PATCH] gs-fonts: add missing module imports Danny Milosavljevic
2017-05-09 10:20 ` bug#26805: [PATCH] gs-fonts: add missing podule imports Ludovic Courtès
2017-05-09 20:36 ` Sergei Trofimovich
2017-05-10 11:53 ` Ludovic Courtès
2017-05-10 20:41 ` Sergei Trofimovich
2017-05-11 20:49 ` Ludovic Courtès
2017-05-14 16:31 ` Sergei Trofimovich
2017-05-14 20:02 ` Ludovic Courtès
2017-05-14 23:15 ` Sergei Trofimovich
2017-05-26 13:02 ` bug#26805: Re-exporting ‘delete’ from (guix build utils) 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
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=20170506154035.23664-1-slyfox@inbox.ru \
--to=slyfox@inbox.ru \
--cc=26805@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 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).