From: Leo Famulari <leo@famulari.name>
To: 47428@debbugs.gnu.org
Subject: bug#47428: Problems building the up-to-date "devel" manual for the website
Date: Fri, 26 Mar 2021 18:36:22 -0400 [thread overview]
Message-ID: <YF5h5v2CkGTl1Xr5@jasmine.lan> (raw)
I noticed that the "devel" version of the online manual, which is
supposed to stay up to date, has not been updated since March 16, 2021:
https://guix.gnu.org/manual/devel/en/
There were some problems related to the recent guile-lib update, which
broke the build scripts in 'doc/build.scm', but that should be fixed
now.
I tried building it with `guix build -f doc/build.scm`, and it crashed
with a segmentation fault while building guix-translated-texinfo.drv,
with this message:
"mmap(PROT_NONE) failed"
I tried again, with --max-jobs=1, and it succeeded. So, maybe we just
need to update and reconfigure ci.guix.gnu.org, and try again.
Here is what I am working with:
------
$ guix describe
Generation 10 Mar 26 2021 20:11:33 (current)
guix e8337f1
repository URL: https://git.savannah.gnu.org/git/guix.git
commit: e8337f1e45b57035c6e5d45133aa9412d4e5e882
------
And, I'm building 'doc/build.scm' from that same commit.
next reply other threads:[~2021-03-26 22:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 22:36 Leo Famulari [this message]
2021-04-01 21:21 ` bug#47428: Problems building the up-to-date "devel" manual for the website Leo Famulari
2021-04-02 7:46 ` Mathieu Othacehe
2021-04-02 8:43 ` Mathieu Othacehe
2021-04-02 9:21 ` Mathieu Othacehe
2021-04-02 9:33 ` Mathieu Othacehe
2021-04-02 21:08 ` Leo Famulari
2021-07-07 18:52 ` Maxim Cournoyer
2021-04-21 15:56 ` Leo Famulari
2021-04-02 19:00 ` Ludovic Courtès
[not found] ` <handler.47428.D47428.162568396228622.notifdone@debbugs.gnu.org>
2021-07-08 7:31 ` Ludovic Courtès
2021-07-08 12:51 ` Maxim Cournoyer
2021-07-09 15:36 ` Ludovic Courtès
2021-07-10 3:56 ` Maxim Cournoyer
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=YF5h5v2CkGTl1Xr5@jasmine.lan \
--to=leo@famulari.name \
--cc=47428@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).