From: "Hans Müller" <mcbeagle@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Out of memory error
Date: Sat, 19 Nov 2011 18:37:59 +0100 [thread overview]
Message-ID: <1684010.yx8ZB1EhLT@sheik-lin> (raw)
In-Reply-To: <CAA2qdGVccVXg7FeOL=r4c+HgjDOxXqp3PD2o2C57=QKf1DPUnw@mail.gmail.com>
On Saturday, 19. November 2011 20:08:36 Pandu Poluan wrote:
> > On Nov 19, 2011 7:28 PM, "Michael Mol" <mikemol@gmail.com> wrote:
> > And, finally, yeah..that isn't just "not much", that's a terribly small
> > amount of memory. Assuming you've kept the software current, some of your
> > applications have certainly not been maintained with 600MB of system
> > memory in mind.
>
> Indeed. With less than 800MB, gcc fails to upgrade. Always. For some
> RAM-constrained systems (e.g. the VMs in my company's cloud), I even have
> to do an "out-of-the-box" upgrade, i.e., upgrade an identical copy on the
> physical data center, grab the binpkg tarball, and upload the tarball to
> the cloud.
If you provide enough swap this shouldn't be an issue.
I have a box running Xen dom0 with 680MB RAM and 1.5GB swap and it compiles
everything fine so far.
Of course I didn't emerge firefox, libreoffice or similar packages on this
system, but at least for gcc this is fine.
Best regards
next prev parent reply other threads:[~2011-11-19 17:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 6:53 [gentoo-user] Out of memory error on gentoo kernel 3.0.6 Mick
2011-11-18 17:42 ` [gentoo-user] Re: Out of memory error Mick
2011-11-19 9:13 ` Nikos Chantziaras
2011-11-19 11:29 ` Mick
2011-11-19 12:25 ` Michael Mol
2011-11-19 13:08 ` Pandu Poluan
2011-11-19 17:37 ` Hans Müller [this message]
2011-11-20 18:48 ` Mick
2011-11-20 19:31 ` Dale
2011-11-19 12:42 ` Nikos Chantziaras
2011-11-19 15:57 ` Volker Armin Hemmann
2011-11-19 17:04 ` Mick
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=1684010.yx8ZB1EhLT@sheik-lin \
--to=mcbeagle@gmx.de \
--cc=gentoo-user@lists.gentoo.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