-
Notifications
You must be signed in to change notification settings - Fork 6
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
Problem with JS scrips on PATH #6
Comments
The I think a good solution would be to update webR's Makefiles for building Wasm system libraries so that they copy any useful host-compatible scripts into I'll open a related Issue in r-wasm/webr, then return here once that's been implemented. |
The masking appears to be solved, but now there is a I'm bringing this up as I've just been made aware that, apparently, it is possible to compile the NNG library using emscripten. I'd like to investigate what is currently possible if I can get past this install step. Thanks. |
@georgestagg I can confirm that the issue with 'xz' at least is resolved. After a bit of tweaking to the CMake files, NNG and MbedTLS are compiling! https://github.com/r-universe/shikokuchuo/actions/runs/8639056802/job/23684720195 |
Some R packages fail to build because we put
/opt/webr/wasm/bin
on the PATH at build time. However this dir contains javascript tools, that the host can not execute. Is it really required to have this on the PATH?rwasm/R/build.R
Line 61 in c15083f
For example packages cannot extract a
tar.xz
file because /usr/bin/xz is masked by/opt/webr/wasm/bin/xz
.The text was updated successfully, but these errors were encountered: