make[4]: Entering directory `/usr/local/portage/portage/kdebase-3.2.0_beta1/work/kdebase-3.1.93/kdm/kfrontend' /bin/sh ../../admin/mkinstalldirs /usr/local/portage/portage/kdebase-3.2.0_beta1/image//usr/kde/3.2/bin /bin/sh ../../libtool --silent --mode=install /bin/install -c -p kdm_config /usr/local/portage/portage/kdebase-3.2.0_beta1/image//usr/kde/3.2/bin/kdm_config /bin/sh ../../libtool --silent --mode=install /bin/install -c -p kdm_greet /usr/local/portage/portage/kdebase-3.2.0_beta1/image//usr/kde/3.2/bin/kdm_greet /bin/sh ../../libtool --silent --mode=install /bin/install -c -p krootimage /usr/local/portage/portage/kdebase-3.2.0_beta1/image//usr/kde/3.2/bin/krootimage /bin/sh ../../libtool --silent --mode=install /bin/install -c -p genkdmconf /usr/local/portage/portage/kdebase-3.2.0_beta1/image//usr/kde/3.2/bin/genkdmconf /bin/sh ../../admin/mkinstalldirs /usr/local/portage/portage/kdebase-3.2.0_beta1/image//usr/kde/3.2/lib/kde3 /bin/sh ../../libtool --silent --mode=install /bin/install -c -p kgreet_classic.la /usr/local/portage/portage/kdebase-3.2.0_beta1/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/local/portage/portage/kdebase-3.2.0_beta1/image//usr/kde/3.2/share/config/kdm --face-src ./pics Cannot create parent /usr/local of target directory /usr/local/portage/portage/kdebase-3.2.0_beta1/image//usr/kde/3.2/share/config/kdm: Permission denied make[4]: *** [install-data-local] Error 1 make[4]: Leaving directory `/usr/local/portage/portage/kdebase-3.2.0_beta1/work/kdebase-3.1.93/kdm/kfrontend' make[3]: *** [install-am] Error 2 make[3]: Leaving directory `/usr/local/portage/portage/kdebase-3.2.0_beta1/work/kdebase-3.1.93/kdm/kfrontend' make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory `/usr/local/portage/portage/kdebase-3.2.0_beta1/work/kdebase-3.1.93/kdm/kfrontend' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/usr/local/portage/portage/kdebase-3.2.0_beta1/work/kdebase-3.1.93/kdm' make: *** [install-recursive] Error 1 !!! ERROR: kde-base/kdebase-3.2.0_beta1 failed. !!! Function kde_src_install, Line 162, Exitcode 2 !!! died running make install, kde_src_install:make However, if I: please kdebase-3.2.0_beta1 # cd /usr/local/portage/portage/kdebase-3.2.0_beta1/work/kdebase-3.1.93/kdm/kfrontend please kfrontend # ./genkdmconf --in /usr/local/portage/portage/kdebase-3.2.0_beta1/image//usr/kde/3.2/share/config/kdm --face-src ./pics Information: reading old kdmrc /usr/kde/3.2/share/config/kdm/kdmrc (from kde >= 2.2.x) Information: old kdmrc is from kde >= 3.1 (config version 2.1) The offending command runs fine outside the ebuild script. Even more curious, if I rune "make DESTDIR=<...> destdir=<...> install" by hand, the install apparently completes just fine in image directory. I tried hacking the kde eclass to not run the make install after I did it by hand, but somehow some of the directories under the image dir get deleted and then the subsequent patching fails. Of course, the root problem is that make install fails when it is run from the ebuild.
please kfrontend # emerge info Portage 2.0.49-r15 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r8, 2.6.0-test9) ================================================================= System uname: 2.6.0-test9 i686 AMD Athlon(tm) MP 2000+ Gentoo Base System version 1.4.3.11 ccache version 2.3 [disabled] ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-mp -O2 -ftracer -ffast-math -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -pipe" DISTDIR="/usr/local/portage/distfiles" FEATURES="sandbox autoaddcvs fixpackages" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j1" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/usr/local/portage" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage/ebuilds" SYNC="rsync://rsync.samerica.gentoo.org/gentoo-portage" USE="x86 oss apm avi crypt cups encode foomaticdb gif jpeg libg++ mad mikmod mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib directfb alsa gdbm berkdb slang readline arts tetex aalib bonobo svga ggi tcltk guile ruby mysql postgres X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gtk qt kde motif opengl mozilla cdr 3dnow apache2 atlas dga dvd faad fam fbcon ffmpeg fftw flac gd gstreamer gtk2 gtkhtml imap imlib2 java jikes lcms lmtp mmx moznocompose moznoirc moznomail netcdf nptl nvidia odbc offensive pcap pic plotutils ppds qtmt samba sse stencil-buffer threads tiff transcode usb wmf xml -gnome"
you need to upgrade portage or build outside of the sandbox. This is a known problem.
der, portage 2.0.49-r15 should be a good enough version for this bug to be fixed. I hope this isn't a portage regression. Will check.
you don't somehow have an old portage around do you? This was a sandbox bug that was fixed in .49-r8 and should still be fixed now. It works properly for me using the sandbox on my machine here with 2.0.49-r15, so I'm not sure why it's failing for you. The test here would be to enter the sandbox and try making a directory that already exists.
Caleb, ./genkdmconf --in /usr/local/portage/portage/kdebase-3.2.0_beta1/image//usr/kde/3.2/share/config/kdm --face-src ./pics please notice the "//" in the above eg(/kdebase-3.2.0_beta1/image//usr/kde/) it doesn't look right does it?? could that be the problem?
Imad, the "//" is fine. Multiple path separators are treated as a single one; scripts often generate the this sort of then when building paths automatically. I don't imagine how I could have another version of portage lying around. I have only ever installed portage with itself, so I don't know where an old version could be. "etcat -v portage" reports 2.0.49-r15 installed. please root # emerge --version Portage 2.0.49-r15 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r8, 2.6.0-test9) is all recent. Is there anything else I could check? Well, I am about to go out of town over the weekend, but if more info is still needed when I get back I will try re-emerging this portage or emerging the r-8 version of portage that has the fix and seeing if things work.
giggles1, have you tried what Caleb suggested to test whether it's a sandbox problem? if that is the case just remove "sandbox" from your FEATURES flags and try again. I've had no problems building yesterday, I am doing an emerge -e world right now, should I encounter a problem similar to your I will advise same. HTH
ddebase does install correctly after removing 'sandbox' from FEATURES in make.globals and make.conf
I can't reproduce this on my end with portage 49-r15, and i'm emerging in the sandbox, so there may just be a stray file sitting around where on your machine from an older portage? Anyway, closing as fixed as it works great here in the sandbox. The alternative, as is noted, is to build outside of the sandbox.
