Re: [gentoo-user] emerge troubles

[Jorge Almeida <jalmeida@math.ist.utl.pt>]

On Tue, 14 Feb 2006, Benno Schulenberg wrote:

> Jorge Almeida wrote:
>> Swap was enabled.
>> $ emerge info
>> [...]
>
> Looks fine.
>
> Have you tried emerging gcc again, a few times, and does it fail
> every time in the same spot with the same error?  What error does
Yes. I tried with CFLAGS and CXXFLAGS="", and with MAKEOPTS="-j1".
> kpdf give?  Does it too fail every time at the same place?  Have
 	config.status: executing depfiles commands

 	Good - your configure finished. Start make now

 	make  all-recursive
 	make[1]: Entering directory `/var/tmp/portage/kpdf-3.4.3-r4/work/kpdf-3.4.3'
 	Making all in doc
 	make[2]: Entering directory `/var/tmp/portage/kpdf-3.4.3-r4/work/kpdf-3.4.3/doc'
 	Making all in kpdf
 	make[3]: Entering directory `/var/tmp/portage/kpdf-3.4.3-r4/work/kpdf-3.4.3/doc/kpdf'
 	/usr/kde/3.4/bin/meinproc --check --cache index.cache.bz2 ./index.docbook
 	parser error : out of memory error
 	parser error : out of memory error
 	/bin/sh: line 1:  3831 Segmentation fault      /usr/kde/3.4/bin/meinproc --check --cache index.cache.bz2 ./index.docbook
 	make[3]: *** [index.cache.bz2] Error 139
 	make[3]: Leaving directory `/var/tmp/portage/kpdf-3.4.3-r4/work/kpdf-3.4.3/doc/kpdf'
 	make[2]: *** [all-recursive] Error 1
 	make[2]: Leaving directory `/var/tmp/portage/kpdf-3.4.3-r4/work/kpdf-3.4.3/doc'
 	make[1]: *** [all-recursive] Error 1
 	make[1]: Leaving directory `/var/tmp/portage/kpdf-3.4.3-r4/work/kpdf-3.4.3'
 	make: *** [all] Error 2

 	!!! ERROR: kde-base/kpdf-3.4.3-r4 failed.
 	!!! Function kde_src_compile, Line 217, Exitcode 2
 	!!! died running emake, kde_src_compile:make
 	!!! If you need support, post the topmost build error, NOT this status message.

(Always at the same place.)
> you tried closing memory-hungry apps like Firefox?  Have you maybe
No memory-hungry apps are open, since I'm working through ssh (and there
are no other human users).
> changed the memory timings in the BIOS lately?  Perhaps it is time
Never touched that. The computer is about 1 year old (but I think the
RAM is generic, so I would think about bad RAM, only I can't confirm it
through testing...)
> to dust off the computer on the inside and reseat the mem chips?
Perhaps, but that's a somewhat frightening idea!
>
> Benno
>
Thanks.

Jorge
-- 
gentoo-user@gentoo.org mailing list