From: Benjamin Slade <beoram@gmail.com>
To: help-guix@gnu.org
Subject: "xmu not found" issue trying to build zutty package
Date: Fri, 27 Dec 2024 18:08:20 -0600 [thread overview]
Message-ID: <87ed1shdor.fsf@gmail.com> (raw)
Hi Guix,
I'm trying to build the Zutty terminal emulator on Guix and, no matter whether I include `libxmu` as an input, native input, or propagated input, the `waf-build` seems to report that 'xmu' cannot be found. (See partial .drv output below:)
,----
| .....
| patch-shebang: ./waf: changing `/usr/bin/env python3' to `/gnu/store/lp8ch4rn10whzyajnzv216d2a2v163c7-python-3.10.7/bin/python3'
| phase `patch-source-shebangs' succeeded after 0.0 seconds
| starting phase `configure'
| running "python waf" with command "configure" and parameters ("--prefix=/gnu/store/f5k6r24kwpyfc2vpg61n81x7rrf8qm06-zutty-0.16")
| Setting top to : /tmp/guix-build-zutty-0.16.drv-0/source
| Setting out to : /tmp/guix-build-zutty-0.16.drv-0/source/build
| Zutty version : 0.16
| Debug build : no
| Checking for 'g++' (C++ compiler) : /gnu/store/86fc8bi3mciljxz7c79jx8zr4wsx7xw8-gcc-11.4.0/bin/g++
| Target platform : Linux
| Checking for program 'pkg-config' : /gnu/store/a3lsdsalcmg5wnk67869af7wljprkbam-pkg-config-0.29.2/bin/pkg-config
| Checking for 'freetype2' : yes
| Checking for 'xmu' : not found
| The configuration failed
| (complete log in /tmp/guix-build-zutty-0.16.drv-0/source/build/config.log)
| error: in phase 'configure': uncaught exception:
| %exception #<&invoke-error program: "python" arguments: ("waf" "configure" "--prefix=/gnu/store/f5k6r24kwpyfc2vpg61n81x7rrf8qm06-zutty-0.16") exit-status: 1 term-signal: #f stop-signal: #f>
| phase `configure' failed after 0.5 seconds
| command "python" "waf" "configure" "--prefix=/gnu/store/f5k6r24kwpyfc2vpg61n81x7rrf8qm06-zutty-0.16" failed with status 1
| build process 10 exited with status 256
`----
(Here's the current pkgbuild I've got so far: <http://paste.debian.net/1341458/> )
I've tried to look for similar issues for Guix package builds, but the only thing I could find was an IRC log where it's in fact me asking about the same issue about 3 years ago ( <https://logs.guix.gnu.org/guix/2022-05-28.log> ) though I'd forgotten I'd tried this before and hit the same issue.
Why is the waf-build not able to recognise that `xmu` is available (no matter where I try including `libxmu`)? Is there something to do to make it visible? Do I need to modify the build sequence in some way?
[Zutty's a pretty interesting terminal emulator, see <https://tomscii.sig7.se/zutty/> ]
thanks,
—Benjamin
--
'(Dr Benjamin Slade (he/him)
(website . <https://lambda-y.net>)
`(pgp_fp: ,(B20E 444C FA80 B5F8 15FA 4AD8 6FBF CD68 3B05 2B84))
"sent by [mu4e] 1.12.8 in [Emacs] 30.0.92 with [org-msg] on [GNU Guix] ([Linux])")
[mu4e] <https://www.djcbsoftware.nl/code/mu/mu4e.html>
[Emacs] <https://www.gnu.org/software/emacs/>
[org-msg] <https://github.com/jeremy-compostella/org-msg>
[GNU Guix] <https://guix.gnu.org/>
[Linux] <https://opensource.com/resources/linux>
next reply other threads:[~2024-12-28 0:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-28 0:08 Benjamin Slade [this message]
2024-12-28 2:40 ` "xmu not found" issue trying to build zutty package 宋文武 via
2024-12-28 6:54 ` Benjamin Slade
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=87ed1shdor.fsf@gmail.com \
--to=beoram@gmail.com \
--cc=help-guix@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.
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).