Summary: | gnome-base/nautilus-2.4.2 failed, Function einstall, Line 388, Exitcode 2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kimmo Sundqvist <kimmo.sundqvist> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kimmo Sundqvist
2004-03-16 01:18:15 UTC
it shouldn't really matter, if you have that much problems i rather expect hardware trouble or something. Does it fail reproducable at _exactly_ the same spot every time ? Anyway, the only thing i can think of here is your makeopts, try if -j1 does a better job. Didn't help. I did "emerge pkgconfig intltool glib libxml2 ORBit2 libIDL libbonobo", and libbonobo failed at (Function einstall, Line 388, Exitcode 2), and after that tried "emerge nautilus" three times, but it always got into an infinite loop (filed a separate bug). But libbonobo will fail exactly at the same place, no matter what dependencies I re-emerge, what optimizations or MAKEOPTS I use. Or what do you suggest? I'll do "emerge world -e" while waiting for something to change. I'll use MAKEOPTS="-j1", and have only 279 ebuilds to do. The machine is a Celeron 433MHz btw, i'm not sure about this, but is a mendocino celeron really a pentium2 ? Isn't it a i586/pentium ? And in general, if all of this fails for you i really strongly suggest you check your machine's health, this works for anyone out there. I actually doubt its a problem on our side if you have so much and all these different failures everywhere. Recompiling kernel, including PIIx -> enabling DMA, disabling APIC and doing "emerge world -e" fixed the underlying problem. I'll see what else I can do with the machine. |