From: David Zafman <dzafman@redhat.com>
To: Jai <jai_97@rediffmail.com>, Nathan Cutler <ncutler@suse.cz>
Cc: dang@redhat.com, Loic Dachary <loic@dachary.org>,
ceph-devel@vger.kernel.org
Subject: Re: make error while building ceph
Date: Tue, 1 Mar 2016 20:07:43 -0800 [thread overview]
Message-ID: <56D6670F.9070803@redhat.com> (raw)
In-Reply-To: <CAPpuMWw6dO9SMwKciX-_GmnzbzU-jUh2RsjH1gjpWd_YvdikKA@mail.gmail.com>
Jai,
On my build machine with 8GB of RAM a make -j4 works fine. So I don't
see why 4GB shouldn't handle a straight make. YMMV
David
On 3/1/16 6:59 PM, Jai wrote:
> I ve got 8G on my laptop - so I can retry with something less than
> that for the VM. Ive reinstalled Centos7 and gone back to gcc 4.8.5
> which is the default on centos 7.
> cmake - I ve tried it, got errors here too.
> --
> Jai
>
> On Wed, Mar 2, 2016 at 1:45 AM, Nathan Cutler <ncutler@suse.cz> wrote:
>> On 03/01/2016 03:39 PM, Jai wrote:
>>> I saw one report of a RAM issue.
>>> I have 2G on the VM - and it was hung for > half a day.
>>
>> I've found that compiling Ceph requires at least 8GB of RAM - anything less
>> is a recipe for failure. I have not tried using cmake, though.
>>
>> --
>> Nathan Cutler
>> Software Engineer Distributed Storage
>> SUSE LINUX, s.r.o.
>> Tel.: +420 284 084 037
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-03-02 4:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 10:29 make error while building ceph Jai
2016-02-28 10:48 ` Loic Dachary
2016-02-28 10:55 ` Jai
2016-02-28 11:09 ` Loic Dachary
2016-02-29 14:34 ` Jai
2016-02-29 15:15 ` Loic Dachary
2016-02-29 17:13 ` Jai
2016-02-29 17:34 ` Loic Dachary
2016-03-01 13:45 ` Daniel Gryniewicz
2016-03-01 14:39 ` Jai
2016-03-01 20:15 ` Nathan Cutler
2016-03-02 2:59 ` Jai
2016-03-02 4:07 ` David Zafman [this message]
2016-03-02 4:19 ` Robert LeBlanc
2016-03-02 6:40 ` Jai
2016-03-04 9:58 ` Jai
2016-03-04 10:53 ` John Spray
2016-03-04 18:44 ` Jai
2016-03-09 9:17 ` Jai
2016-03-30 20:59 ` Noah Watkins
2016-03-30 22:18 ` Josh Durgin
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=56D6670F.9070803@redhat.com \
--to=dzafman@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dang@redhat.com \
--cc=jai_97@rediffmail.com \
--cc=loic@dachary.org \
--cc=ncutler@suse.cz \
/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