From: Norbert Kamenicky <noro@xmedia.sk>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Howto continue after failed emerge
Date: Sat, 07 Jun 2003 13:25:59 +0200 [thread overview]
Message-ID: <3EE1CBC7.2070909@xmedia.sk> (raw)
In-Reply-To: <200306071239.03841.pauldv@gentoo.org>
Paul de Vrieze wrote:
>On Saturday 07 June 2003 11:45, Norbert Kamenicky wrote:
>
>
>>Hi,
>>
>>I added support for slovak language to openoffice-1.0.3-r1.ebuild, and
>>tried it to emerge.
>>
>>After 11 hours (5 h localization !!! + 6 h compilation)
>>it fails on missing file ...
>>How can I continue without waiting another 11 hours ?
>>
>>Noro
>>
>>
>>
>>
>
>ebuild /usr/portage/app-office/openoffice/openoffice-1.0.3-r1.ebuild compile
>ebuild /usr/portage/app-office/openoffice/openoffice-1.0.3-r1.ebuild install
>ebuild /usr/portage/app-office/openoffice/openoffice-1.0.3-r1.ebuild package
>ebuild /usr/portage/app-office/openoffice/openoffice-1.0.3-r1.ebuild qmerge
>
This looks very nice ... :-)
but I once tried to run "ebuid some_another.ebuid compile", but it
deleted source tree
and made it again (I haven't ccache emerged ... mayby that's the reason ?)
since I started emerge with USE and LANGUAGE flags is it necessary to run
"USE="x" LANGUAGE="x" ebuild path_to/office.ebuild compile" or all
environment
will be catched from temp/environment ?
>Do all this, then all compiled files will stay where they are and will not be
>recompiled.
>
>Paul
>
>
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-06-07 11:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-07 9:45 [gentoo-dev] Howto continue after failed emerge Norbert Kamenicky
2003-06-07 10:01 ` gabor
2003-06-07 10:10 ` Philippe Lafoucrière
2003-06-07 16:24 ` Daniel Armyr
2003-06-07 10:39 ` Paul de Vrieze
2003-06-07 11:25 ` Norbert Kamenicky [this message]
2003-06-07 11:34 ` Paul de Vrieze
-- strict thread matches above, loose matches on Subject: below --
2003-06-07 9:53 Norbert Kamenicky
2003-06-08 10:44 ` Norbert Kamenicky
2003-06-08 14:51 ` Georgi Georgiev
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=3EE1CBC7.2070909@xmedia.sk \
--to=noro@xmedia.sk \
--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