Created attachment 349108 [details] gcc-config-logs.tar.bz2 Emerging gcc 4.7.3 gives the following (masking does not help, same happens with older versions) ibtool: link: /usr/x86_64-pc-linux-gnu/bin/ranlib .libs/libgfortran.a libtool: link: ( cd ".libs" && rm -f "libgfortran.la" && ln -s "../libgfortran.la" "libgfortran.la" ) make[6]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.7.3/work/build/x86_64-pc-linux-gnu/32/libgfortran' make[5]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.7.3/work/build/x86_64-pc-linux-gnu/32/libgfortran' make[4]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.7.3/work/build/x86_64-pc-linux-gnu/libgfortran' make[3]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.7.3/work/build/x86_64-pc-linux-gnu/libgfortran' make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.7.3/work/build/x86_64-pc-linux-gnu/libgfortran' make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.7.3/work/build' >>> Source compiled. * --------------------------- ACCESS VIOLATION SUMMARY --------------------------- * LOG FILE: "/var/log/sandbox/sandbox-14373.log" * VERSION 1.0 FORMAT: F - Function called FORMAT: S - Access Status FORMAT: P - Path as passed to function FORMAT: A - Absolute Path (not canonical) FORMAT: R - Canonical Path FORMAT: C - Command Line F: open_wr S: deny P: /usr/include/DONE A: /usr/include/DONE R: /usr/include/DONE C: touch /usr/include/DONE F: utimensat S: deny P: /usr/include/DONE A: /usr/include/DONE R: /usr/include/DONE C: touch /usr/include/DONE F: open_wr S: deny P: /usr/include/DONE A: /usr/include/DONE R: /usr/include/DONE C: touch /usr/include/DONE F: utimensat S: deny P: /usr/include/DONE A: /usr/include/DONE R: /usr/include/DONE C: touch /usr/include/DONE * -------------------------------------------------------------------------------- * * Please include /var/tmp/portage/sys-devel/gcc-4.7.3/work/build/gcc-build-logs.tar.bz2 in your bug report *
In this tarball, there are only config.logs, which, while eventually potentially useful, won't help much without build log, which you've failed to attach. Though such failure hints you're likely have mess in your environment.
Created attachment 349192 [details] build.log.bz2 Here is a recent build log (not sure sure why it isn't in gcc-build-logs.tar.bz2, it says "build-logs" after all) I only get this problem when emerging gcc, not with other packages, so I'm not sure what's suddenly changed in my environment to cause this Thanks in advance
Well, going by the build log, it seems it's not environment after all, but (probably) something on the filesystem. Things go wrong quite early - shortly after line 3049 of the log. Check two things: - if reemerging freetype help - what owns /usr/include/DONE and - if possible - how it got created
*** This bug has been marked as a duplicate of bug 434180 ***
Many thanks! After reading the follow up comments the culprit turned out to be the double slash in the following symlink: /usr/include/freetype -> //usr/lib64/freetype2/include Replacing with link with a single slash fixed it. How this relates to the sandbox errors is not clear to me though. It seems gcc is vulnerable to this double slash issue, are other packages too? Also, from reading the duplicate bug it would be prudent to include build.log in gcc-build-logs.tar.bz2 (or the tarball should be called something less confusing)
