Igor Korot posted on Mon, 26 Nov 2012 12:50:34 -0800 as excerpted:
> Hi, guys,
> I got mDNSResponder and restarted emerge.
> It went OK for some time and then stopped with following:
>
> * Messages for package kde-base/ksvg-3.5.10:
>
> * ERROR: kde-base/ksvg-3.5.10 failed (install phase):
> * emake install failed.
OK, you got thru the build phase, but kde3 used to (for me, it's used to,
I've been on kde4 since before kde3 got "sunset") do an awful lot in the
install phase as well, and that's what's screwing up. (Note that the
"install phase" is still the "fake install", to the location under
$PORTAGE_TMPDIR, the real install is called qmerge, and simply copies
everything from the fake install under $PORTAGE_TMPDIR to the live
system.)
But....
> * The specific snippet of code:
> * emake DESTDIR="${D}" destdir="${D}" install || \
> * die "emake install failed.";
> * The complete build log is located at
> '/var/tmp/portage/kde-base/ksvg-3.5.10/temp/build.log'.
... you included the portage error, but not the make install
log with its error... and you didn't include an emerge --verbose
--pretend or similar, to see the USE flags it used, either!
The easiest way to find the first error is often to either grep for or
open the log file in your favorite editor and search for, "error". With
a lot of packages the first few hits will be on errorlog or whatever
modules, but then you'll start hitting the errors that triggered the
die. You'll want to post at least the code surrounding the first one.
(I usually backup from there until I find the "entering whatever-subdir"
line before the error, and post from there thru the "leaving whatever
subdir" line after the error, when I bug-file, then attach the whole
build-log as well, just in case it's needed.)
> * IMPORTANT: 3 news items need reading for repository 'gentoo'.
> * Use eselect news to read news items.
Unlikely to be apropos here, but you let news items build up without
reading them? You /do/ realize that's a good way to get an unbootable
system or the like, because you failed to follow the instructions in the
news items and thus didn't do the necessary updates that they warned you
about, right?
Ideally, you read news items right away, before emerging anything (at
least once eselect itself is merged), just as you always either to an
emerge --pretend --verbose first or use emerge --ask, to see what it's
going to do and check its sanity (plus look for any USE flag changes and/
or what the flags are on new packages, making changes as necessary),
before actually letting portage do it.
Similarly, after you're done with your updates, it's always a good idea
to run revdep-rebuild, etc-update (or the like), and emerge --depclean
(don't forget the --ask/--pretend first!), to keep the cruft to a minimum.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
