Rob, This seems to be something to do with selinux. Apparently the linker defaults to requiring an executable stack unless all the files that make up the module contain a special directive to say they don't require it. Output from g++ does contain the marker but the hand-coded assembly code in Poly/ML doesn't. It probably wouldn't be hard to fix this but it I'm a bit concerned about adding a directive to the assembly code which might cause it to break on some systems. Alternative ways round it are to add options to the assembler or linker lines.

As a temporary measure you can adjust the selinux settings to avoid checking for an executable stack.

Regards, David

Rob Arthan wrote:

I get the following failure when I try to build Poly/ML on a Fedora 12 box:

... ./polyimport -H 10 polytemp.txt -I . < ./exportPoly.sml /home/rda/bld/poly/polyml.5.3/.libs/lt-polyimport: error while loading shared libraries: libpolyml.so.1: cannot enable executable stack as shared object requires: Permission denied

Any suggestions gratefully received,

Regards,

Rob. _______________________________________________ polyml mailing list polyml@inf.ed.ac.uk http://lists.inf.ed.ac.uk/mailman/listinfo/polyml