-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Error: librsvg-2.so.2: cannot enable executable stack as shared object requires: #3917
Comments
@Lc0rE This could be an issue with sharp and WSL. It looks like there's some suggested workarounds over at lovell/sharp-libvips#3 |
Sorry, I forgot to mention that I tried to follow the steps proposed in the sharp issue you linked. Trying to invoke the command Since, as far as I understand, There is a sharp folder in |
Ok apparently I solved the issue like this:
At this point, invoking
Now it's working.. hope it helps! |
|
@Lc0rE: Thanks a lot! Could this workaround be somehow added to sharp build script? For me this single command sufficed:
Current long-term fix for me is this command as
Edit: Note: With recent sharp and node the workaround above may not be needed anymore and could cause a build error. |
Description
After upgrading both
gatsby-cli
and all thegatsby-*
dependencies and plugins in thepackage.json
, I'm facing the following error invokinggatsby-develop
:Environment
Gatsby version: 1.9.183
Node.js version: 8.9.4
Operating System: Windows 10 on WSL (Ubuntu)
Any ideas on what could cause this unexpected behavior? This only occurs on the WSL substrate on Windows 10. I tested it on macOS and it works fine.
I tried to delete both
node_modules
,.cache/
andbuild/
folders but nothing changed.The text was updated successfully, but these errors were encountered: