Summary: | sys-devel/gcc-4.7.3 - access violation in `touch /usr/include/DONE' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gordon Wells <gordon.wells> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
gcc-config-logs.tar.bz2
build.log.bz2 |
Description
Gordon Wells
2013-05-24 22:22:37 UTC
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) |