From: "AJ Spagnoletti" <rubiks120@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Stop and continue emerge -e world
Date: Tue, 14 Mar 2006 18:44:20 -0500 [thread overview]
Message-ID: <a39c95ee0603141544h308e0860w23aa34140b073679@mail.gmail.com> (raw)
In-Reply-To: <20060314231828.272822e7@krikkit.digimed.co.uk>
> Not so. emerge --resume restarts the previous emerge process, even after
> a reboot, exactly as Petr needs.
Just a note when you issue an emerge --resume, if you stopped the
emerge in the middle of a compile it will not pick up in the middle it
will start compiling that package from the beginning again.
> I doubt the fact that some packages are compiled with one GCC and others
> with a different one is going to cause a problem, especially as you'll
> carry on with the recompiling after the reboot. Even if you don't reboot,
> your system will be running with a mixture of 3.3/3.4-compiled packages
> during the emerge.
>
I have a slower computer (celeron 800 mhz) and a family that doesnt
like to leave the computer on all the time so when I ran my gcc
upgrade it took close to a week and I didnt encounter any problems
during this time with a system that was only partially recompiled with
GCC 3.4.
A.J.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-15 0:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 22:39 [gentoo-user] Stop and continue emerge -e world Petr Uzel
2006-03-14 22:53 ` Petr Uzel
2006-03-14 23:09 ` Unknown
2006-03-14 23:18 ` Neil Bothwick
2006-03-14 23:32 ` Petr Uzel
2006-03-14 23:48 ` Unknown
2006-03-15 8:56 ` Neil Bothwick
2006-03-15 14:10 ` Michael Sullivan
2006-03-16 0:25 ` Iain Buchanan
2006-03-14 23:44 ` AJ Spagnoletti [this message]
2006-03-14 23:36 ` JimD
2006-03-14 23:42 ` Patrick Börjesson
2006-03-15 0:24 ` Petr Uzel
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=a39c95ee0603141544h308e0860w23aa34140b073679@mail.gmail.com \
--to=rubiks120@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