unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 47428-done@debbugs.gnu.org
Subject: bug#47428: Problems building the up-to-date "devel" manual for the website
Date: Wed, 21 Apr 2021 11:56:38 -0400	[thread overview]
Message-ID: <YIBLNgkTJyKc+J6i@jasmine.lan> (raw)
In-Reply-To: <87k0plghdm.fsf@gnu.org>

On Fri, Apr 02, 2021 at 11:33:57AM +0200, Mathieu Othacehe wrote:
> 
> > ). Please consider running po4a-updatepo to refresh it.
> > Your input po file ./guix-manual.de.po seems outdated (The amount of entries differ between files: 10012 is not 325
> > ). Please consider running po4a-updatepo to refresh it.
> > mmap(PROT_NONE) failed
> > builder for `/gnu/store/86gnwxxw7lfkifaal6fhflmkn3fczyhf-guix-translated-texinfo.drv' failed due to signal 11 (Segmentation fault)
> 
> I worked around it by building this derivation on one core. Looks like
> the cookbook, website, manual and devel manual are now building fine.

The problem happened again.

How can we make sure this derivation is always single-threaded?




  parent reply	other threads:[~2021-04-21 15:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26 22:36 bug#47428: Problems building the up-to-date "devel" manual for the website Leo Famulari
2021-04-01 21:21 ` 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 [this message]
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=YIBLNgkTJyKc+J6i@jasmine.lan \
    --to=leo@famulari.name \
    --cc=47428-done@debbugs.gnu.org \
    --cc=othacehe@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).