From: Gabriel Hondet via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 66222@debbugs.gnu.org
Subject: bug#66222: Fail to build guix documentation
Date: Tue, 26 Sep 2023 22:51:30 +0200 [thread overview]
Message-ID: <ZRNEUq3FvnxAj9OF@eryngii> (raw)
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
Hello,
I was trying to setup guix following the steps given in
https://guix.gnu.org/manual/en/html_node/Building-from-Git.html
I already have the Guix package manager installed, so, in the checked
out repository, I enter a suitable shell using `guix shell -D guix
help2man git strace guile --pure`.
Then if I run `make`, the process fails and prints out
make[2]: Entering directory '/home/g/src/guix'
MAKEINFO doc/guix.de.info
contributing.de.texi:1571: @menu reference to nonexistent node
`Configuring Git'
contributing.de.texi:1572: @menu reference to nonexistent node
`Sending a Patch Series'
make[2]: *** [Makefile:4977: doc/guix.de.info] Error 1
make[2]: Leaving directory '/home/g/src/guix'
make[1]: *** [Makefile:6096: all-recursive] Error 1
make[1]: Leaving directory '/home/g/src/guix'
make: *** [Makefile:4210: all] Error 2
while I was expecting nothing but a 0 return code.
For context, I use the Guix package manager (commit
c173819c8e5235ce02d60b79bd88b10023a7c614) on top of Void Linux.
Cheers,
Gabriel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-09-27 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 20:51 Gabriel Hondet via Bug reports for GNU Guix [this message]
2023-09-27 13:16 ` bug#66222: Fail to build guix documentation Tobias Geerinckx-Rice via Bug reports for GNU Guix
[not found] ` <handler.66222.D66222.169582061915967.notifdone@debbugs.gnu.org>
2023-09-28 7:09 ` bug#66222: closed (Re: Fail to build guix documentation) Gabriel Hondet via Bug reports for GNU Guix
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZRNEUq3FvnxAj9OF@eryngii \
--to=bug-guix@gnu.org \
--cc=66222@debbugs.gnu.org \
--cc=gabriel.hondet@laposte.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.