public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jorge Almeida <jalmeida@math.ist.utl.pt>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] compiling problems
Date: Wed, 16 Nov 2005 16:31:51 +0000 (WET)	[thread overview]
Message-ID: <Pine.LNX.4.63.0511161629240.8983@weber.math.ist.utl.pt> (raw)
In-Reply-To: <7573e9640511160818t58d1c31u7c1643e2b764d47@mail.gmail.com>

On Wed, 16 Nov 2005, Richard Fish wrote:

> Probably not, because it isn't gcc that is failing...it is
> gtkdoc-mkhtml, and it is running out of memory.
> 
> You can either merge gtk with USE=-doc, which will skip this step, or
> use MAKEFLAGS=-j1, which will run only one process at a time, and
> reduce your memory requirements by about half.
That makes sense, since I only recently set MAKEFLAGS=-j2 (it was
recommended, I think). RAM is 512M and swap is about 760M. Could this be
the cause?
> 
 
Jorge 
-- 
gentoo-user@gentoo.org mailing list



      reply	other threads:[~2005-11-16 16:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 11:44 [gentoo-user] compiling problems Jorge Almeida
2005-11-16 16:18 ` Richard Fish
2005-11-16 16:31   ` Jorge Almeida [this message]

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=Pine.LNX.4.63.0511161629240.8983@weber.math.ist.utl.pt \
    --to=jalmeida@math.ist.utl.pt \
    --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