public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joshua Murphy" <poisonbl@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] openoffice emerge failing
Date: Fri, 21 Nov 2008 12:51:14 -0500	[thread overview]
Message-ID: <c30988c30811210951l14a4928ey6780e2a8e55e81e0@mail.gmail.com> (raw)
In-Reply-To: <20081121141713.GE32114@anton.digitaltorque.ca>

On Fri, Nov 21, 2008 at 9:17 AM, Michael P. Soulier
<msoulier@digitaltorque.ca> wrote:
> On 20/11/08 Michael P. Soulier said:
>> On 20/11/08 Redouane Boumghar said:
>> > SO please check how much available memory you have
>>
>> I have 1Gig in this system, and I'm planning to add more.
>
> So, I killed firefox to free up memory and let it build overnight. The build
> completed successfully. Perhaps it was a memory issue.
>
> I'm starting to think that ebuilds need available memory requirements. Don't
> build this without 1Gig of free memory, etc...
>
> Anywho, it works now.
>
> Mike
> --
> Michael P. Soulier <msoulier@digitaltorque.ca>
> "Any intelligent fool can make things bigger and more complex... It takes a
> touch of genius - and a lot of courage to move in the opposite direction."
> --Albert Einstein

Both RAM and disk space are non-issues on my system[1] and last
night's ooo rebuild still managed to fail (too far away from my logs
to see that error easily, but pretty sure it was module 'sw' rather
than 'chart2'). I restarted it this morning, but didn't get to stay
and watch... and I'll be out of town all weekend. Maybe next week I'll
have time to see if it's willing to cooperate... same general error
message as OP, but different place in the build.

[1] 4GB ram, less than 1gb used when I'm not compiling, and I was
building ooo with portage temp pointed toward my half-empty 500GB
drive (since it wasn't going to fit in tmpfs like nearly everything
else does).

-- 
Poison [BLX]
Joshua M. Murphy



  reply	other threads:[~2008-11-21 17:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20 12:39 [gentoo-user] openoffice emerge failing Michael P. Soulier
2008-11-20 12:42 ` Qian Qiao
2008-11-20 12:48   ` Michael P. Soulier
2008-11-20 12:49     ` deface
2008-11-20 12:59       ` Dirk Heinrichs
2008-11-20 13:10         ` Florian Philipp
2008-11-21  0:19           ` Iain Buchanan
2008-11-21  0:26             ` Paul Hartman
2008-11-21  6:51               ` Dirk Heinrichs
2008-11-21  6:52               ` Daniel Pielmeier
2008-11-21 15:25                 ` Paul Hartman
2008-11-20 13:14         ` Dirk Uys
2008-11-20 13:24           ` Dirk Heinrichs
2008-11-20 20:22             ` Dale
2008-11-20 13:37       ` Michael P. Soulier
2008-11-20 14:11         ` Philip Webb
2008-11-20 12:55     ` Qian Qiao
2008-11-20 14:51       ` Michael P. Soulier
2008-11-20 15:11         ` Dirk Heinrichs
2008-11-20 14:29     ` Redouane Boumghar
2008-11-20 14:54       ` Michael P. Soulier
2008-11-21 14:17         ` Michael P. Soulier
2008-11-21 17:51           ` Joshua Murphy [this message]
2008-11-23  9:13           ` Jorge Peixoto de Morais Neto
2008-11-21  0:27       ` Iain Buchanan
2008-11-21  9:11         ` Redouane Boumghar

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=c30988c30811210951l14a4928ey6780e2a8e55e81e0@mail.gmail.com \
    --to=poisonbl@gmail.com \
    --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