SEO

#1 (**permalink**) 02-21-2008, 10:31 AM

What is the emerge to cause recompile of everything
and is it inadvisable aside from taking forever?
I had some scsi problems that caused node issues.
The basic system is intact for the most part but
I have noted strange quirks arising from missing
parts. Biggest one is KDE starts strangely slow
and sometimes not at all.
I know a lot of the missing parts are kde, mostly
useless glitz but may be some important stuff. This
is because I looked at the nodes dropped in lost+found.
Directories are easy to move back but guessing files
can be hard

Thanks for any pointers.
-Walt

#2 (**permalink**) 02-21-2008, 10:31 AM

PenguinsAnonymous@notAchance.org wrote:
> What is the emerge to cause recompile of everything
> and is it inadvisable aside from taking forever?
> I had some scsi problems that caused node issues.
> The basic system is intact for the most part but
> I have noted strange quirks arising from missing
> parts. Biggest one is KDE starts strangely slow
> and sometimes not at all.
> I know a lot of the missing parts are kde, mostly
> useless glitz but may be some important stuff. This
> is because I looked at the nodes dropped in lost+found.
> Directories are easy to move back but guessing files
> can be hard

>
> Thanks for any pointers.
> -Walt

emerge --sync
emerge -e --pretend world | tee /emerge.txt
less /emerge.txt

but you might find kde-base might block. If you do you have to emerge -C
each of the blocking modules

Then finally: emerge -e world

You can also use emerge --resume if things break.

#3 (**permalink**) 02-21-2008, 10:31 AM

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 29 Sep 2005 09:42:23 +1000, glowworm
<glowworm@mailinator.com> probably wrote (unless it was a Kook):
> emerge --sync
> emerge -e --pretend world | tee /emerge.txt
> less /emerge.txt
>
> but you might find kde-base might block. If you do you have to emerge -C
> each of the blocking modules
>
> Then finally: emerge -e world
>
> You can also use emerge --resume if things break.

You may want to emerge ccache, which will speed up those KDE split builds.

- --
eval join"",map{chomp;s/^.+>\s*//;$_}grep{/>/}<DATA>; __DATA__
.' .' Kelly "STrRedWolf" Price -- WolfSkunk Designs
xX xX .' http://stalag99.net tygris @ same domain
"X "X X .'
_____. X" X > 0;
XXXXXXXx. X".' > 0;
'"XXXXXX| X > 0;
"XXX| X" > 0;
'XX' > 0;
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDO/pWRCiTQGVX194RAs5WAJ9u2U+K7x+YEQKRWRBLft3h+EIwIQCe JlP3
FuZuEuneA3Na+Lkr3d8n29E=
=XWGU
-----END PGP SIGNATURE-----

#4 (**permalink**) 02-21-2008, 10:32 AM

Kelly Price wrote:
> On Thu, 29 Sep 2005 09:42:23 +1000, glowworm
> <glowworm@mailinator.com> probably wrote (unless it was a Kook):
>
>>>emerge --sync
>>>emerge -e --pretend world | tee /emerge.txt
>>>less /emerge.txt
>>>
>>>but you might find kde-base might block. If you do you have to emerge -C
>>>each of the blocking modules
>>>
>>>Then finally: emerge -e world
>>>
>>>You can also use emerge --resume if things break.
>
>
> You may want to emerge ccache, which will speed up those KDE split builds.
>
Hey Kelly, I didn't know about that pacakge. Thanks for the hint.

From the web: "ccache is a fast compiler cache. When you compile a
program, it will cache intermediate results so that, whenever you
recompile the same program, the compilation time is greatly reduced. In
common compilations this can result in 5 to 10 times faster compilation
times."

I am emerging ccache right now.

#5 (**permalink**) 02-21-2008, 10:32 AM

glowworm <glowworm@mailinator.com> wrote:
> Kelly Price wrote:
>> On Thu, 29 Sep 2005 09:42:23 +1000, glowworm
>> <glowworm@mailinator.com> probably wrote (unless it was a Kook):
>>
>>>> emerge --sync
>>>> emerge -e --pretend world | tee /emerge.txt
>>>> less /emerge.txt
>>>>
>>>> but you might find kde-base might block. If you do you have to
>>>> emerge -C each of the blocking modules
>>>>
>>>> Then finally: emerge -e world
>>>>
>>>> You can also use emerge --resume if things break.
>>
>>
>> You may want to emerge ccache, which will speed up those KDE split
>> builds.
>>
> Hey Kelly, I didn't know about that pacakge. Thanks for the hint.
>
> From the web: "ccache is a fast compiler cache. When you compile a
> program, it will cache intermediate results so that, whenever you
> recompile the same program, the compilation time is greatly reduced.
> In common compilations this can result in 5 to 10 times faster
> compilation times."
>
> I am emerging ccache right now.

ccache is great. The only thing to be aware of is that you should zonk
the cache whenever upgrading gcc. If you see gcc in the list of
upgrades when doing emerge --pretend, emerge gcc seperately, then zap
the ccache before building the rest. Else, ccache has a tendency to use
the old object files created with an older gcc version.

Oh, and you might want to do "ln -s /var/tmp/ccache ~/.ccache" as root
too, so root shares the ccache with portage (which compiles as root
anyhow), and you can do "ccache -s" to get stats.

Regards,
--
*Art

#6 (**permalink**) 02-21-2008, 10:32 AM

Arthur Hagen wrote:

> If you see gcc in the list of
> upgrades when doing emerge --pretend, emerge gcc seperately, then zap
> the ccache before building the rest. Else, ccache has a tendency to use
> the old object files created with an older gcc version.

Yes, thats a valid point. Would you also have to clear your ccache if
you changed the CFLAGS? Otherwise you could half one compile method and
half another !!

So, back to the OP's question... Would this mean if you were doing an
emerge -e world with ccache you really should do this to be safe?

emerge --sync
emerge --update --pretend gcc
Look if the version changes {
rm /var/tmp/ccache/
emerge --update --deep gcc
}
emerge -e world

I would assume doing it this way would ensure your gcc was the exact
same version before you went ahead and recompiled everything?

#7 (**permalink**) 02-21-2008, 10:33 AM

glowworm <glowworm@mailinator.com> wrote:
> Arthur Hagen wrote:
>
>> If you see gcc in the list of
>> upgrades when doing emerge --pretend, emerge gcc seperately, then zap
>> the ccache before building the rest. Else, ccache has a tendency to
>> use the old object files created with an older gcc version.
>
> Yes, thats a valid point. Would you also have to clear your ccache if
> you changed the CFLAGS? Otherwise you could half one compile method
> and half another !!

No, it catches that -- it's only taken from cache if both the source
file and the parameters (including CFLAGS) are identical. It's just
when the executable producing the object file (gcc/ld/icc/ar/...) has
changed that you need to watch out.

> So, back to the OP's question... Would this mean if you were doing an
> emerge -e world with ccache you really should do this to be safe?
>
> emerge --sync
> emerge --update --pretend gcc
> Look if the version changes {
> rm /var/tmp/ccache/
> emerge --update --deep gcc
> }
> emerge -e world
>
> I would assume doing it this way would ensure your gcc was the exact
> same version before you went ahead and recompiled everything?

Yes, that's the safest method (you need rm -rf, though, or better yet,
if you have the symlink to ~/.ccache, you can do "ccache -C" to clear
it).

I just do
emerge --pretend --update --deep world
[visual scan for gcc]
emerge --update --deep world # if it looks ok

Regards,
--
*Art

#8 (**permalink**) 02-21-2008, 10:33 AM

Ok I'm feeling a little queazy about this. Is it a
fairly safe thing to do? What are the chances of
total failure?
My system is working as is although this quirk with
a daemon for KDE exists and causes the splash to hang
although eventually completing the desktop start.
I'm weighing the risk vs the potential for further
problem here.
I just did an emerge world and had no problem doing it
so it seems the problem(s) have not affected portage.
Advice?
Thanks.
-Walt

glowworm <glowworm@mailinator.com> wrote:
> PenguinsAnonymous@notAchance.org wrote:
>> What is the emerge to cause recompile of everything
>> and is it inadvisable aside from taking forever?
>> I had some scsi problems that caused node issues.
>> The basic system is intact for the most part but
>> I have noted strange quirks arising from missing
>> parts. Biggest one is KDE starts strangely slow
>> and sometimes not at all.
>> I know a lot of the missing parts are kde, mostly
>> useless glitz but may be some important stuff. This
>> is because I looked at the nodes dropped in lost+found.
>> Directories are easy to move back but guessing files
>> can be hard

>>
>> Thanks for any pointers.
>> -Walt
>
> emerge --sync
> emerge -e --pretend world | tee /emerge.txt
> less /emerge.txt
>
> but you might find kde-base might block. If you do you have to emerge -C
> each of the blocking modules
>
> Then finally: emerge -e world
>
> You can also use emerge --resume if things break.

--
--

email replies to innkeepATncDOTrrDOTcom please.

#9 (**permalink**) 02-21-2008, 10:39 AM

Arthur Hagen wrote:
> Oh, and you might want to do "ln -s /var/tmp/ccache ~/.ccache" as root
> too, so root shares the ccache with portage (which compiles as root
> anyhow), and you can do "ccache -s" to get stats.

THAT is why `ccache -s' seems not working... thanks! I'll soon update the
gentoo-wiki ccache howto, if it's not already done...

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

rebuild whole system