Sage Dev Staff: Yes, the clean build was successful after setting the SE Linux configuration to "Permissive". There was an alert by SE Linux that the ccl application (the compiler) was trying to make the stack executable after the attempt to build Pari failed. I thought it was some sort of bug. I was able to configure and build Pari by hand and the build of ntl then complained that a shared object file was trying to make the stack executable upon loading as an explanation for why the build of ntl failed.
I'm not sure why the applications in question make the stack executable. It may be an efficiency or performance thing. If so, then there is a fundamental conflict between performance and security (not surprising). As for a command line way to check the status of SE Linux, I'll check and see what I can find. At a minimum, it appears that one needs SE Linux set to "Permissive" in order to build sage, at least under the Fedora Core 12 OS. I'm sure "Disabled" works as well, but the build will fail if set to "Enforced". My understanding is that it doesn't matter whether you're "root" or not. SE Linux if set to "Enforced" will cause the build of Sage to fail because some applications and libraries in the Sage system set the stack to be executable, and SE Linux views that as a security risk. John Bussoletti -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org To unsubscribe from this group, send email to sage-support+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
