Summary: | gcl-2.6.7-r3 fails to compile on x86 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
Component: | Current packages | Assignee: | Common Lisp Bugs <common-lisp> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | david.morgan, Martin.vGagern |
Priority: | High | ||
Version: | 2007.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Juergen Rose
2007-09-01 09:20:48 UTC
There is something subtle going on. You get this error on amd64 when you remove flag-o-matic from the inherit line. But the problem are not the x86_64 systens, there the compilation of gcl-2.6.7-r3 works. Only at all (seven) i686 systen the installation fails. (In reply to comment #2) > But the problem are not the x86_64 systens, there the compilation of > gcl-2.6.7-r3 works. Only at all (seven) i686 systen the installation fails. > Just to be clear, gcl-2.6.7-r3 does NOT compile on AMD64 (x86_64) for me. I get the same error as the original reporter. I'm getting the exact same error, also on amd64. Just to inform you, there is a problem with sandbox, gentoo-lisp team is working to solve it.Anyway, gcl is very broken. I don't know if it has future.We'll see. There used to be a workaround mentioned in bug 161041, looking at the diff I guess it was exporting SANBOX_ON=0. According to the ChangeLog this workaround was commented out when the debian patches 34 were included to resolve bug 190631. However that bug says nothing about the sandbox issue, and from this bug here you can tell it's still a problem. Can we get the workaround in place again till bug 164656 has been resolved? I've put back one of the workarounds, not sure if it is enough, and I have put a comment there to explain why it is there. At least now I know why it is there :) *** This bug has been marked as a duplicate of bug 161041 *** |