-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Issue with sandbox.sh #4454
Comments
Out of curiosity, why did you added the environment variable on |
I originally had I have several debian systems (both buster and testing) and the problem is consistent across all. Just to verify I installed a fresh version of Debian 10 (buster) in a virtual machine ( |
It is the same behavior than reading a file from
Can you try something similar, to check if it comes only from the sandbox not reading from |
I can confirm that the above example works as expected. |
@rjbou - is this definitely to fix for 2.1? |
@kit-ty-kate - does #4795 eliminate this? |
Unless @drjdn was that the case? |
@kit-ty-kate Nope, I have no symlinks in `/usr/local`
|
Closing this for now, as it doesn't appear that there's anything which we need to alter. Please feel free to re-open with any additional information, though, if it's still not working! |
I'm unable to build ocaml-r via
opam
. If I clone the repo and build usingdune
it compiles correctly. On my system R is installed at prefix/usr/local/R
which is not where it would generally be installed if using a package manager. I'm pretty sure it is related tosandbox.sh
since:fails with a message about missing shared libraries. However, if I
cd
into:and run:
it builds correctly. I've tried adding the appropriate paths to
OPAM_USER_PATH_RO
via:but it still fails to build correctly. I've tried
/usr/local/R/lib/R/lib
wherelibR.so
lives and various other attempts like/usr/local/R
but nothing has worked. Not sure if this is a bug or if I'm not understanding howopam
sandboxing works. You can find further discussion about this between me and the author ofocaml-r
at PR14.Result of
opam config report
:The text was updated successfully, but these errors were encountered: