The issue does not look gentoo 1.3 specific so I post it here ;) emerge fails because kdebase make install apparently tries to mkdir /root/.kde, which conflicts with the sandbox that is enabled per default.
Please provide more information: the actual output with the error in it and 2-3 paragraphs before it.
Here is a cut and paste from an xterm with make install: make[3]: Entering directory `/var/tmp/portage/kdebase-3.0.2/work/kdebase-3.0.2/doc/kdm' make[3]: Circular index.cache.bz2 <- index.cache.bz2 dependency dropped. /usr/kde/3/bin/meinproc --check --cache index.cache.bz2 ./index.docbook ACCESS DENIED mkdir: /root/.kde trying to create local folder: Permission denied failed to create /root/.kde/share/config/ ACCESS DENIED mkdir: /root/.kde trying to create local folder: Permission denied failed to create /root/.kde/share/config/ make[3]: Leaving directory `/var/tmp/portage/kdebase-3.0.2/work/kdebase-3.0.2/doc/kdm' Making all in kate make[3]: Entering directory `/var/tmp/portage/kdebase-3.0.2/work/kdebase-3.0.2/doc/kate' make[3]: Circular index.cache.bz2 <- index.cache.bz2 dependency dropped. /usr/kde/3/bin/meinproc --check --cache index.cache.bz2 ./index.docbook ACCESS DENIED mkdir: /root/.kde trying to create local folder: Permission denied failed to create /root/.kde/share/config/ ACCESS DENIED mkdir: /root/.kde trying to create local folder: Permission denied failed to create /root/.kde/share/config/ [...] Making all in faq make[4]: Entering directory `/var/tmp/portage/kdebase-3.0.2/work/kdebase-3.0.2/doc/khelpcenter/faq' make[4]: Circular index.cache.bz2 <- index.cache.bz2 dependency dropped. ACCESS DENIED mkdir: /root/.kde trying to create local folder: Permission denied failed to create /root/.kde/share/config/ ACCESS DENIED mkdir: /root/.kde trying to create local folder: Permission denied /usr/kde/3/bin/meinproc --check --cache index.cache.bz2 ./index.docbook failed to create /root/.kde/share/config/ and so on.
This is strange. I can't reproduce it and I can't find anything in the makefiles to explain it. Are you sure this is the src_install phase, and that the src_compile phase finished ok without access errors? Can you reproduce this when running make install manually? I.e. after emerge fails, go to the builddir. Move ~/.kde/share/config somewhere (while not reunning kde obviously) so that we can test whether or not it'll try to create that directory. Goto e.g. doc/kdm and run: make install DESTDIR=/var/tmp/portage/kdebase-3.0.2/image And see if it creates ~/.kde/share/config. (Then move it back.) Oh, and if you didn't know, you can disable sandboxing to install kdebase and bypass the problem while this is under investigation.
I just ran "emerge kdebase" again and I noticed that the first errors appear during the _configure_ run! Here is a cut-and-paste: [...] checking for artsc-config... /usr/kde/3/bin/artsc-config checking for kde-config... /usr/kde/3/bin/kde-config checking for meinproc... /usr/kde/3/bin/meinproc ACCESS DENIED mkdir: /root/.kde trying to create local folder: Permission denied failed to create /root/.kde/share/config/ ACCESS DENIED mkdir: /root/.kde trying to create local folder: Permission denied failed to create /root/.kde/share/config/ ACCESS DENIED mkdir: /root/.kde trying to create local folder: Permission denied failed to create /root/.kde/share/config/ ACCESS DENIED mkdir: /root/.kde trying to create local folder: Permission denied failed to create /root/.kde/share/config/ checking for PAM... yes checking for const pam_message... const: Linux-type PAM checking for getspent in -lshadow... yes checking for shadow passwords... yes [...]
Aha! Now we can pinpoint the location of the errors. At least the configure ones. Can you please post your config.log? I tied reading the configure script and correlating with the output you posted but didn't find any obvious culprits. config.log should have them.
n/m that, I've reproduced it. I don't have time for it atm because I'm working on kde 3.1 alpha1 ebuilds and have lots of people clamouring for them all over the place :-) But, I'll get onto it tomorrow.
*** Bug 3504 has been marked as a duplicate of this bug. ***
Everyone: is this still relevant? The sandbox has been reworked in the latest versions of portage, and in my expirience, although access is denied the build process doesn't abort because of it.
Comments from Felix von Leitner <leitner@fefe.de>: The build process now continues and at least konqueror works. -- Felix: replying to bugzilla's notifications doesn't work, the comment isn't added to the bugreport. You have to add it the regular way.
I believe this has been fixed. Please reopen if needed. I'd be very interested in hearing at what precise point/upgrade this was fixed.
