From: Thomas Koenig <tkoenig@netcologne.de>
To: Damian Rouson <damian@sourceryinstitute.org>,
GNU GFortran <fortran@gcc.gnu.org>
Subject: Re: Bootstrap build failure on Linux
Date: Sat, 24 Oct 2015 17:21:00 -0000 [thread overview]
Message-ID: <562BBE01.2090503@netcologne.de> (raw)
In-Reply-To: <092A0AA4-EFE9-40C1-9713-DC9A00FFE4C7@sourceryinstitute.org>
Am 24.10.2015 um 19:07 schrieb Damian Rouson:
> collect2: fatal error: ld terminated with signal 9 [Killed]
Signal 9 is SIGKILL, which unconditionally kills a process.
It is not part of the normal boot process.
SIGKILL is something that is sent by the Linux OOM (Out Of Memory)
killer, so this is something that might have happened. If so,
I would expect a corresponding message in the log file.
As to why - either your system was low on memory due to other reasons,
or there was a problem with the build which manifested itself by
using excessive memory during linking.
HTH
Thomas
next prev parent reply other threads:[~2015-10-24 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 17:07 Damian Rouson
2015-10-24 17:15 ` Steve Kargl
2015-10-24 17:18 ` Damian Rouson
2015-10-24 17:21 ` Thomas Koenig [this message]
2015-10-24 18:21 ` Damian Rouson
2015-10-25 2:16 ` Damian Rouson
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=562BBE01.2090503@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=damian@sourceryinstitute.org \
--cc=fortran@gcc.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.
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).