From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Adam Kandur <rndd@tuta.io>
Cc: 44096@debbugs.gnu.org
Subject: bug#44096: failed to build wesnoth
Date: Tue, 20 Oct 2020 12:15:06 +0200 [thread overview]
Message-ID: <87sga98aqd.fsf@nckx> (raw)
In-Reply-To: <MK4RomV--3-2@tuta.io>
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
Adam,
This is probably not a bug:
Adam Kandur via Bug reports for GNU Guix 写道：
> c++: internal compiler error: Killed (program cc1plus)
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <https://gcc.gnu.org/bugs/> for instructions.
> make[2]: *** [src/CMakeFiles/wesnoth-core.dir/build.make:183:
> src/CMakeFiles/wesnoth-core.dir/gettext_boost.cpp.o] Error 4
> make[2]: Leaving directory
> '/tmp/guix-build-wesnoth-1.14.14.drv-0/build'
> make[1]: *** [CMakeFiles/Makefile2:402:
> src/CMakeFiles/wesnoth-core.dir/all] Error 2
> make[1]: *** Waiting for unfinished jobs....
...which often happens when you run out of RAM, or due to other
system-level failure.
Take a look in your dmesg for any out-of-memory (OOM) or other
errors at that time.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-10-20 10:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 9:59 bug#44096: failed to build wesnot Adam Kandur via Bug reports for GNU Guix
2020-10-20 10:15 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-10-20 12:40 ` bug#44096: failed to build wesnoth Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-10-31 9:49 ` bug#44096: failed to build wesnot Arun Isaac
2021-11-01 10:48 ` Arun Isaac
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=87sga98aqd.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=44096@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=rndd@tuta.io \
/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.