unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "宋文武 via" <help-guix@gnu.org>
To: Benjamin Slade <beoram@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: "xmu not found" issue trying to build zutty package
Date: Sat, 28 Dec 2024 10:40:59 +0800	[thread overview]
Message-ID: <87frm8fs1w.fsf@envs.net> (raw)
In-Reply-To: <87ed1shdor.fsf@gmail.com> (Benjamin Slade's message of "Fri, 27 Dec 2024 18:08:20 -0600")

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.


  reply	other threads:[~2024-12-28  2:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-28  0:08 "xmu not found" issue trying to build zutty package Benjamin Slade
2024-12-28  2:40 ` 宋文武 via [this message]
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=87frm8fs1w.fsf@envs.net \
    --to=help-guix@gnu.org \
    --cc=beoram@gmail.com \
    --cc=iyzsong@envs.net \
    /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).