All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willem Jan Withagen <wjw@digiware.nl>
To: "James (Fei) Liu-SSI" <james.liu@ssi.samsung.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: FW: G++ internal compiler error
Date: Wed, 10 Feb 2016 01:18:03 +0100	[thread overview]
Message-ID: <56BA81BB.2030906@digiware.nl> (raw)
In-Reply-To: <99767EA2E27DD44DB4E9F9B9ACA458C0561C17D6@SSIEXCH-MB3.ssi.samsung.com>

On 10-2-2016 01:10, James (Fei) Liu-SSI wrote:
> 
> Hi All,
>  Compiler errors against Ceph master. Any clues?
>  Here is my g++ version :
>  g++ (Ubuntu 4.8.4-2ubuntu1~14.04) 4.8.4
>  Copyright (C) 2013 Free Software Foundation, Inc.
>  This is free software; see the source for copying conditions.  There is NO
>  warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> 
> Errors output:
> CXX      mon/MonCap.lo
>   CXX      mon/MonClient.lo
>   CXX      mon/MonMap.lo
>   CXX      osd/OSDMap.lo
>   CXX      osd/osd_types.lo
> g++: internal compiler error: Killed (program cc1plus)
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
> make[3]: *** [mon/MonCap.lo] Error 1
> make[3]: *** Waiting for unfinished jobs....
> make[3]: Leaving directory `/home/jamesliu/WorkSpace/omni_ceph/src'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/home/jamesliu/WorkSpace/omni_ceph/src'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/home/jamesliu/WorkSpace/omni_ceph/src'
> make: *** [all-recursive] Error 1

I've seen this this happen when compiling in a small VM with too much
parallel and running out of swap. (actually the VM did not have any swap
configured.)

--WjW



  reply	other threads:[~2016-02-10  0:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10  0:10 FW: G++ internal compiler error James (Fei) Liu-SSI
2016-02-10  0:18 ` Willem Jan Withagen [this message]
2016-02-10  0:19 ` Somnath Roy
2016-02-10  0:51   ` James (Fei) Liu-SSI

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=56BA81BB.2030906@digiware.nl \
    --to=wjw@digiware.nl \
    --cc=ceph-devel@vger.kernel.org \
    --cc=james.liu@ssi.samsung.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.
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.