Summary: | sys-devel/gcc-4.8.1 sandbox violations when running fix includes step | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Patrick Lauer <patrick> |
Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | info, pgsql-bugs, trilader+gentoobugs |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build log
build log |
Description
Patrick Lauer
2013-06-27 06:47:22 UTC
Created attachment 360514 [details]
build log
For me I could fix this issue by deleting the following symlinks in /usr/include which look like remains from a postgres installation: lrwxrwxrwx 1 root root 5 15. Jul 17:27 libpq -> ../.. lrwxrwxrwx 1 root root 5 15. Jul 17:27 libpq-fe.h -> ../.. lrwxrwxrwx 1 root root 5 15. Jul 17:27 pg_config_manual.h -> ../.. lrwxrwxrwx 1 root root 5 15. Jul 17:27 postgres_ext.h -> ../.. lrwxrwxrwx 1 root root 14 15. Jul 17:27 postgresql -> postgresql-9.2 I simply removed them as I don't have postgresql installed anymore. After removing them gcc emerges without problems. I tried different versions of gcc. I'm getting this in any >=4.7 (have not tried <4.7) must be something on the system, but what? The libpq stuff Daniel mentioned didn't do it for me. (In reply to Darko Luketic from comment #3) > I tried different versions of gcc. I'm getting this in any >=4.7 (have not > tried <4.7) must be something on the system, but what? The libpq stuff > Daniel mentioned didn't do it for me. If you are still getting access violations post them here like Patrick did. Also there could be other broken symlinks in your /usr/include if thats causing the problems for you. (In reply to Daniel Schulte from comment #4) > (In reply to Darko Luketic from comment #3) > > I tried different versions of gcc. I'm getting this in any >=4.7 (have not > > tried <4.7) must be something on the system, but what? The libpq stuff > > Daniel mentioned didn't do it for me. > > If you are still getting access violations post them here like Patrick did. > Also there could be other broken symlinks in your /usr/include if thats > causing the problems for you. It compiled, it was just me being dumb/ unable to read properly. I checked the sandbox log and saw the files mentioned and they were relatively linked and were pointing to non-existing files. Thanks Daniel. OK whatever change in postgres caused this was long in the past, so closing the bug now as obsolete. |