Making install in doc make[1]: Entering directory `/var/lib/portage/tmp/portage/dvthread-0.4.6a/work/dvthread-0.4.6a/doc' make[2]: Entering directory `/var/lib/portage/tmp/portage/dvthread-0.4.6a/work/dvthread-0.4.6a/doc' /bin/sh ../mkinstalldirs -m 0755 /usr/share/dvthread/download mkdir -m 0755 -p -- /usr/share/dvthread/download [31;01mACCESS DENIED[0m mkdir: /usr/share/dvthread mkdir: cannot create directory `/usr/share/dvthread': Permission denied make[2]: *** [install-exec-local] Error 1 make[2]: Leaving directory `/var/lib/portage/tmp/portage/dvthread-0.4.6a/work/dvthread-0.4.6a/doc' make[1]: *** [install-am] Error 2 make[1]: Leaving directory `/var/lib/portage/tmp/portage/dvthread-0.4.6a/work/dvthread-0.4.6a/doc' make: *** [install-recursive] Error 1 !!! ERROR: dev-libs/dvthread-0.4.6a failed. !!! Function src_install, Line 23, Exitcode 2 !!! (no error message) !!! If you need support, post the topmost build error, NOT this status message. --------------------------- ACCESS VIOLATION SUMMARY -------------------------- LOG FILE = "/tmp/sandbox-dev-libs_-_dvthread-0.4.6a-13888.log" mkdir: /usr/share/dvthread -------------------------------------------------------------------------------- ...done! ================================================================================ Yes, I *am* running the emerge as root! ... :-) Here are the permissions on /usr/share: dwn@memphis dwn $ ls -ld /usr/share drwxr-xr-x 216 root root 6144 Jun 7 18:17 /usr/share Also, there are a couple of gigabytes of free space on my /usr filesystem, so it isn't a space problem masquerading as an access violation. The /usr filesystem is mounted as read/write. So, there doesn't seem to be any reason for the access violation. In fact, I emerged dvutil immediately prior to this and that worked just fine. This earlier ebuild built /usr/share/dvutil and populated it without incident. This directory is on the same physical filesystem as /usr/share/dvthread would have been had the dvthread ebuild worked.
This issue should be fixed in 0.4.7-r2. I'll have a closer look when I get home in the morning and either a) mark 0.4.7-r2 stable, or b) backport the fix.
Fixed. Thanks for the report.
