Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot enable executable stack on Ubuntu on Windows #11

Closed
adrien-n opened this issue Aug 24, 2017 · 2 comments
Closed

Cannot enable executable stack on Ubuntu on Windows #11

adrien-n opened this issue Aug 24, 2017 · 2 comments

Comments

@adrien-n
Copy link

Hi,

For « fun » I decided to try to build Prose (the collaborative text editor) on Windows/Ubuntu through its recent Linux subsystem. Well, for fun and to find out whether this subsystem could handle non-trivial workloads which include builds and packaging.

Build worked but ocsigenserver failed at runtime with the following error message:

Error: Error on dynamically loaded library: /home/prose/.opam/4.04.2/lib/stublibs/dllzarith.so: /home/prose/.opam/4.04.2/lib/stublibs/dllzarith.so: cannot enable executable stack as shared object requires: Invalid argument\n

I don't know if the requirement on an executable stack comes from Zarith or from GMP so maybe I'm filling this issue report in the wrong project.

antoinemine pushed a commit that referenced this issue Aug 24, 2017
…y default for .S files, which is useless for us and only cause trouble; see issue #11)
@antoinemine
Copy link
Collaborator

Zarith should not require an executable stack. However, I just discovered that compiling assembly files with gcc (unlike C files) produces objects with executable stacks by default, which is probably the source of your problem. I've pushed a fix that adds the required assembly directive to ask for a non-executable stack. I've checked, only on Linux x86_64, that it indeed produces an so file with non-executable stack.
Could you please check whether your problem does away with this patch?

@adrien-n
Copy link
Author

Yes, this fixed the issue, thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants