From: Zheng Junjie <zhengjunjie@iscas.ac.cn>
To: 67358@debbugs.gnu.org
Subject: [bug#67358] [PATCH core-updates] gnu: fontforge: fix build.
Date: Wed, 22 Nov 2023 11:29:23 +0800 [thread overview]
Message-ID: <5c50257d5e2a87099249c3e52c03a5ec0e91f1a2.1700623763.git.zhengjunjie@iscas.ac.cn> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 1550 bytes --]
This follows up on commit 3f2c6cc3933bc01077383e4ff83b6a5d00f83129.
gnu/packages/fontutils.scm(fontforge)[arguments]<#:phase>: adjust input names.
Change-Id: I64c3992e995294cb04a9f4c79cd841bfc51ba08d
---
gnu/packages/fontutils.scm | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/fontutils.scm b/gnu/packages/fontutils.scm
index 9a0f09b1e1..d933382ede 100644
--- a/gnu/packages/fontutils.scm
+++ b/gnu/packages/fontutils.scm
@@ -18,6 +18,7 @@
;;; Copyright © 2023 gemmaro <gemmaro.dev@gmail.com>
;;; Copyright © 2023 John Kehayias <john.kehayias@protonmail.com>
;;; Copyright © 2023 Janneke Nieuwenhuizen <janneke@gnu.org>
+;;; Copyright © 2023 Zheng Junjie <873216071@qq.com>
;;;
;;; This file is part of GNU Guix.
;;;
@@ -1597,9 +1598,9 @@ (define-public fontforge
,(map (lambda (input)
(string-append (assoc-ref inputs input)
"/lib"))
- '("libtiff" "libjpeg" "libpng" "libungif"
+ '("libtiff" "libjpeg-turbo" "libpng" "libungif"
"libxml2" "zlib" "libspiro" "freetype"
- "pango" "cairo" "fontconfig")))
+ "pango" "cairo" "fontconfig-minimal")))
;; Checks for potrace program at runtime
`("PATH" ":" prefix (,potrace)))))))))
(synopsis "Outline font editor")
base-commit: 1bca46690c6240310befc6208fb24a044bd4b437
--
2.41.0
next reply other threads:[~2023-11-22 3:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 3:29 Zheng Junjie [this message]
2023-11-22 14:03 ` bug#67358: [PATCH core-updates] gnu: fontforge: fix build Hilton Chain 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
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=5c50257d5e2a87099249c3e52c03a5ec0e91f1a2.1700623763.git.zhengjunjie@iscas.ac.cn \
--to=zhengjunjie@iscas.ac.cn \
--cc=67358@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).