These are the last lines I get from emerging the new kde

/bin/sh ../../libtool --silent --mode=install /bin/install -c -p kgreet_classic.la /usr/portage/tmp/portage/kdebase-3.2.0/image//usr/kde/3.2/lib/kde3/kgreet_classic.la
libtool: install: warning: remember to run `libtool --finish /usr/kde/3.2/lib/kde3'
../genkdmconf --in /usr/portage/tmp/portage/kdebase-3.2.0/image//usr/kde/3.2/share/config/kdm --face-src ./pics
Cannot create parent /usr/portage of target directory /usr/portage/tmp/portage/kdebase-3.2.0/image//usr/kde/3.2/share/config/kdm: Permission denied
make[4]: *** [install-data-local] Error 1
make[4]: Leaving directory `/usr/portage/tmp/portage/kdebase-3.2.0/work/kdebase-3.2.0/kdm/kfrontend'
make[3]: *** [install-am] Error 2
make[3]: Leaving directory `/usr/portage/tmp/portage/kdebase-3.2.0/work/kdebase-3.2.0/kdm/kfrontend'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory `/usr/portage/tmp/portage/kdebase-3.2.0/work/kdebase-3.2.0/kdm/kfrontend'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/usr/portage/tmp/portage/kdebase-3.2.0/work/kdebase-3.2.0/kdm'
make: *** [install-recursive] Error 1

!!! ERROR: kde-base/kdebase-3.2.0 failed.
!!! Function kde_src_install, Line 185, Exitcode 2
!!! died running make install, kde_src_install:make


What must I do now?

Matata

On Fri, 13 Feb 2004 15:29:17 +0100, Matata wrote:

>
> !!! ERROR: kde-base/kdebase-3.2.0 failed.
> !!! Function kde_src_install, Line 185, Exitcode 2
> !!! died running make install, kde_src_install:make
>
>
> What must I do now?
>

I'm no guru, but I made my life easier since I started to use, emerging
such apps like qt, kde and openoffice i.e. very "sensitive" and taking
much time, with the X stopped and e.g.:
emerge -f kde||emerge kde||emerge kde||emerge kde||emerge kde||emerge
kde||emerge kde||emerge kde||emerge kde||emerge kde||emerge kde

That way, I leave it for the night and the next day: voila! emerged.
This helps mostly with segmentation faults but sometimes with other
errors. although your error doesn't seem to be a segmentation fault but
meanwhile, until somebody helps you, this might help as well

PiotrAF wrote:

> On Fri, 13 Feb 2004 15:29:17 +0100, Matata wrote:
>
>>
>> !!! ERROR: kde-base/kdebase-3.2.0 failed.
>> !!! Function kde_src_install, Line 185, Exitcode 2
>> !!! died running make install, kde_src_install:make
>>
>>
>> What must I do now?
>>
>
> I'm no guru, but I made my life easier since I started to use, emerging
> such apps like qt, kde and openoffice i.e. very "sensitive" and taking
> much time, with the X stopped and e.g.:
> emerge -f kde||emerge kde||emerge kde||emerge kde||emerge kde||emerge
> kde||emerge kde||emerge kde||emerge kde||emerge kde||emerge kde
>
> That way, I leave it for the night and the next day: voila! emerged.
> This helps mostly with segmentation faults but sometimes with other
> errors. although your error doesn't seem to be a segmentation fault but
> meanwhile, until somebody helps you, this might help as well

Looks like you could do with down-clocking your system.

Styvaen.

On Fri, 13 Feb 2004 22:59:40 +0000, Styvaen wrote:

> Looks like you could do with down-clocking your system.

and what do you mean by that?

PiotrAF wrote:

> On Fri, 13 Feb 2004 22:59:40 +0000, Styvaen wrote:
>
>> Looks like you could do with down-clocking your system.
>
> and what do you mean by that?

Random segfaults like that indicate that there's something
wrong with your hardware.

--
* Andreas Klauer | ~'' L@@k at Nerd Boy!
* Menaures (a) UNItopia | >> .\\. http://www.Nerd-Boy.net
telnet://UNItopia.de | __ |\ __ dd ______________________
http://www.UNItopia.de - deutschsprachiges Online-Textadventure MUD

On Sat, 14 Feb 2004 03:15:08 +0100, Andreas Klauer wrote:

>>> Looks like you could do with down-clocking your system.
>>

Still don't know what was meant by that

> Random segfaults like that indicate that there's something
> wrong with your hardware.

Yes, I've herd it a million times. Strange that it happens on most of my
machines and even after changing that hardware. Besides, It's not a
problem and a hint to others. There is no harm in "||" even if you have a
superhardware - it will always stop if it finishes the emerge the first
time, and my life with gentoo would have been much easier a year ago if
someone instead of telling me I have broken hardware gave me such hint

On Sat, 14 Feb 2004 11:00:35 +0100, PiotrAF wrote:

>On Sat, 14 Feb 2004 03:15:08 +0100, Andreas Klauer wrote:
>
>>>> Looks like you could do with down-clocking your system.
>>>
>
>Still don't know what was meant by that
>
>> Random segfaults like that indicate that there's something
>> wrong with your hardware.
>
>Yes, I've herd it a million times. Strange that it happens on most of my
>machines and even after changing that hardware. Besides, It's not a
>problem and a hint to others. There is no harm in "||" even if you have a
>superhardware - it will always stop if it finishes the emerge the first
>time, and my life with gentoo would have been much easier a year ago if
> someone instead of telling me I have broken hardware gave me such hint

I had an overclocked athlon xp and whilst I didn't see segmentation faults
whilst compiling I did see cpu errors when encoding video (only from dmesg
not encoder stderr). Some were recoverable, some not. After dropping the
multiplier these errors ceased completely. With intensive compiling you're
quite likely to get similar problems. I know very little about the
compiling process, but I believe it's possible to generate flawed
executables without seeing segfaults or problems that halt the compile.

On Sat, 14 Feb 2004 11:34:25 +0000, Dean Edwards wrote:

>
> I had an overclocked athlon xp and whilst I didn't see segmentation faults
> whilst compiling I did see cpu errors when encoding video (only from dmesg
> not encoder stderr). Some were recoverable, some not. After dropping the
> multiplier these errors ceased completely. With intensive compiling you're
> quite likely to get similar problems. I know very little about the
> compiling process, but I believe it's possible to generate flawed
> executables without seeing segfaults or problems that halt the compile.

No, I don't overclock anything on any PC and all the systems are stable.
Thnx

Matata wrote:

> These are the last lines I get from emerging the new kde
>
> /bin/sh ../../libtool --silent --mode=install /bin/install -c -p
> kgreet_classic.la
> /usr/portage/tmp/portage/kdebase-3.2.0/image//usr/kde/3.2/lib/kde3/kgreet_classic.la
> libtool: install: warning: remember to run `libtool --finish
> /usr/kde/3.2/lib/kde3' ./genkdmconf --in
> /usr/portage/tmp/portage/kdebase-3.2.0/image//usr/kde/3.2/share/config/kdm
> --face-src ./pics Cannot create parent /usr/portage of target
> directory
> /usr/portage/tmp/portage/kdebase-3.2.0/image//usr/kde/3.2/share/config/kdm:
> Permission denied make[4]: *** [install-data-local] Error 1 make[4]:
> Leaving directory

I had the same problem here. I tried some different use flags,
different FEATURES settings, and some other tricks, nothing helped. I
ended up with replacing genkdmconf.c with a fake program which printed
out only the way it was called, then I could run the original
genkdmconf command by hand, and voila - it worked. Well, you gotta
call the command right after it would be issued by make, because it
will fail at a later point if the created directory is not present.


see you

Dave

--
Dave "tPassive" Vogt| ruby -e "n=gets.to_i;a=(2..n).to_a;a.each{
Linux user #225040| |x|puts x;(x*2).step(n,x){|j|a.delete j}}"
____________________|_____________________________ |
PGP Key: http://control-alt-del.ch/public_key.asc \____________/

I've had this problem with the kdebase-3.2.0 ebuild too. You're not alone.
There are plenty of people who've had this problem in the forums. The
solution that's worked for me is to add FEATURES="-sandbox" on the command
line before emerging like so:

FEATURES="-sandbox"
emerge /usr/portage/kde-base/kdebase/kdebase-3.2.0.ebuild

If i simply removed sandbox from the FEATURES line in make.conf, it doesn't
help a damn thing.

Matata wrote:

> `/usr/portage/tmp/portage/kdebase-3.2.0/work/kdebase-3.2.0/kdm' make: ***
> [install-recursive] Error 1
>
> !!! ERROR: kde-base/kdebase-3.2.0 failed.
> !!! Function kde_src_install, Line 185, Exitcode 2
> !!! died running make install, kde_src_install:make
>
>
> What must I do now?
>
> Matata