From: Maxime Devos <maximedevos@telenet.be>
To: xdrcft56 <xdrcft56@protonmail.com>
Cc: 53511@debbugs.gnu.org
Subject: bug#53511: guix pull command fails
Date: Tue, 25 Jan 2022 08:59:40 +0100 [thread overview]
Message-ID: <9963b38d99b3d01186aeed61d8ca346e3dade234.camel@telenet.be> (raw)
In-Reply-To: <HUlrLGynICEibzthGimGKkW6pAdXH50Ywc_PIpNrFjNayqEvcjYNmTLxpU_dgVYmlzHKZESPV6WszqT2wcrwHl0pDgVTAs72_aeoK0TX384=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
xdrcft56 schreef op ma 24-01-2022 om 23:35 [+0000]:
> Thank you. I've attached the requested log file (/var/log/guix/drvs/aj/mmafhpmi83ssxg860wd93z9yhhhk5w-gcc-10.3.0.drv.bz2).
‘collect2: fatal error: ld terminated with signal 9 [Killed]’
this could indicate an out-of-memory situation, which Guix cannot
really do anything about. If it is a OOM, the dmesg should contain a
message about it (I don't know exactly how it looks like). A future
OOM can be avoided by closing some memory intensive applications (e.g.
most web browsers) and reducing the number of cores used for building:
"guix pull --cores=2 --max-jobs=1".
In principle, it could be something else though. Can you reproduce
with "guix pull --cores=2 --max-jobs=1"?
Also, I'm noticing you are building everything from source.
To avoid having to build things (and hence reduce the chance of
an OOM) (and save energy), I recommend enabling and authorising
substitutes.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-01-25 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 18:28 bug#53511: guix pull command fails xdrcft56 via Bug reports for GNU Guix
2022-01-24 21:25 ` Maxime Devos
2022-01-24 23:35 ` xdrcft56 via Bug reports for GNU Guix
2022-01-25 7:59 ` Maxime Devos [this message]
2022-01-25 18:32 ` xdrcft56 via Bug reports for GNU Guix
2022-01-26 18:59 ` xdrcft56 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
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=9963b38d99b3d01186aeed61d8ca346e3dade234.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53511@debbugs.gnu.org \
--cc=xdrcft56@protonmail.com \
/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).