Skip to content
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.

Building SLING on Windows Subsystem for Linux (WSL) #296

Closed
anders-sandholm opened this issue Nov 21, 2018 · 1 comment
Closed

Building SLING on Windows Subsystem for Linux (WSL) #296

anders-sandholm opened this issue Nov 21, 2018 · 1 comment

Comments

@anders-sandholm
Copy link
Contributor

anders-sandholm commented Nov 21, 2018

We currently only support Linux out-of-the-box.

We intend to use this issue to track and document problems with building and using SLING on Windows Subsystem for Linux (WSL) and solutions for this these.

While we do not currently intend to check these into the main code base, it can serve as a guide to those who want to use it on WSL anyway.

@anders-sandholm anders-sandholm changed the title Building SLING on Windows Subsystem Linux (WSL) Building SLING on Windows Subsystem for Linux (WSL) Nov 21, 2018
@anders-sandholm
Copy link
Contributor Author

As noted in #291, on WSL you may come across an executable stack error like:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python2.7/dist-packages/sling/__init__.py", line 1, in <module>
    import pysling as api
ImportError: /usr/lib/python2.7/dist-packages/sling/pysling.so: cannot enable executable stack as shared object requires: Invalid argument

As also reported in #291, using the solution from microsoft/WSL#916 (comment) (i.e. execstack -c /usr/local/lib/opencv.so*) seems to fix the issue. Another option may be to simply disable the executable stacks using the -z noexecstack GCC flag.

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

No branches or pull requests

2 participants