"xmu not found" issue trying to build zutty package

"xmu not found" issue trying to build zutty package

[Benjamin Slade]

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>

Re: "xmu not found" issue trying to build zutty package

[宋文武 via]

Benjamin Slade <beoram@gmail.com> writes:

> 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:)
>

You can add 'libxt' to inputs, run 'pkg-config --cflags libxmu' will
report 'xt' is missing if not.  I'll send a patch to add libxt to
libxmu's 'propagated-inputs' later, usually those kind of indirect
dependencies are handled this way.

Re: "xmu not found" issue trying to build zutty package

[Benjamin Slade]

> You can add 'libxt' to inputs, run 'pkg-config --cflags libxmu' will
> report 'xt' is missing if not.  I'll send a patch to add libxt to
> libxmu's 'propagated-inputs' later, usually those kind of indirect
> dependencies are handled this way.

Many thanks! Adding `libxt' to `inputs' does indeed enable this to now compile. (Have to figure out about default font paths now. But a basic build is now working!)