From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: Binary ebuild for openoffice-ximian
Date: Mon, 17 Nov 2003 11:45:54 +0100 [thread overview]
Message-ID: <200311171145.55332.pauldv@gentoo.org> (raw)
In-Reply-To: <200311161520.13009.ellings@kcnet.com>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 922 bytes --]
On Sunday 16 November 2003 22:20, Steven Elling wrote:
>
> 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?
>
I don't know about the keepwork feature, but running ebuild <path to ebuild>
compile does work similar to normal make, so it saves a lot of time.
Paul
--
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-11-17 10:46 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
2003-11-17 10:45 ` Paul de Vrieze [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=200311171145.55332.pauldv@gentoo.org \
--to=pauldv@gentoo.org \
--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