public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Steven Elling <ellings@kcnet.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: Binary ebuild for openoffice-ximian
Date: Sun, 16 Nov 2003 15:20:11 -0600	[thread overview]
Message-ID: <200311161520.13009.ellings@kcnet.com> (raw)
In-Reply-To: <1068969342.24232.56.camel@localhost>

On Sunday 16 November 2003 01:55, Andrew Cowie wrote:
<snip>
>
> WARNING!
>
> For anyone considering trying building this thing, they really aren't
> kidding when they say it needs > 4.5 GigaBytes
> to build and 12-14 hours to build and packages. It's a real bummer to
> run out of space somewhere around the install/buildpackage/merge step.
> This is an excellent time to use
>
>  	PORTAGE_TMPDIR="/partition/with/lots/of/space/tmp"
>
> on the command line before emerge...

I had the problem of running out of space and the OO build failing because 
of it.  I have since freed up enough space to complete the install, but I 
was curious about something else.

In the event that the OO build fails, can the keepwork feature be used to 
essentially start the build again where it left off.

I know that make will check the modified time on files to determine if 
object files and such should be recompiled, but does qmake or whatever OO 
is using to do the build do the same?  Or, are key files modified that 
force the recompile of all object files?


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-11-16 21:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-13  6:23 [gentoo-dev] Binary ebuild for openoffice-ximian Sebastian Bergmann
2003-11-13  7:29 ` Troy Dack
2003-11-13 12:54   ` [gentoo-dev] " Sebastian Bergmann
2003-11-14  4:44     ` Troy Dack
2003-11-14  8:47       ` Paul de Vrieze
2003-11-14  9:01         ` suka
2003-11-16  7:55           ` Andrew Cowie
2003-11-16  9:31             ` Paul de Vrieze
2003-11-16 21:20             ` Steven Elling [this message]
2003-11-17 10:45               ` Paul de Vrieze

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=200311161520.13009.ellings@kcnet.com \
    --to=ellings@kcnet.com \
    --cc=gentoo-dev@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