Part that fails: make[2]: Entering directory `/var/tmp/portage/gnome-vfs-2.0.1/work/gnome-vfs-2.0.1' make[2]: Nothing to be done for `install-exec-am'. /bin/sh ./mkinstalldirs /var/tmp/portage/gnome-vfs-2.0.1/image//usr/lib/pkgconfig mkdir /var/tmp/portage/gnome-vfs-2.0.1/image/usr/lib/pkgconfig /bin/install -c -m 644 ./gnome-vfs-2.0.pc /var/tmp/portage/gnome-vfs-2.0.1/image//usr/lib/pkgconfig/gnome-vfs-2.0.pc /bin/install -c -m 644 ./gnome-vfs-module-2.0.pc /var/tmp/portage/gnome-vfs-2.0.1/image//usr/lib/pkgconfig/gnome-vfs-module-2.0.pc make[2]: Leaving directory `/var/tmp/portage/gnome-vfs-2.0.1/work/gnome-vfs-2.0.1' make[1]: Leaving directory `/var/tmp/portage/gnome-vfs-2.0.1/work/gnome-vfs-2.0.1' >>> Completed installing into /var/tmp/portage/gnome-vfs-2.0.1/image/ --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-gnome-vfs-2.0.1-1059.log" mkdir: /root/.gconfd -------------------------------------------------------------------------------- !!! emerge aborting on /usr/portage/gnome-base/gnome-vfs/gnome-vfs-2.0.1.ebuild . Log : bash-2.05a$ more /tmp/sandbox-gnome-vfs-2.0.1-1059.log mkdir: /root/.gconfd
mm, unfortunately this snippet didn't contain the real error (thats quite a way up there) but I thought it was cared for... will check again.