-
Notifications
You must be signed in to change notification settings - Fork 35
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 loading otp_spec_fix.erl from escript #74
Labels
Comments
Oops! |
I checked what the escript zip container (using I've tried adding it using escript_incl_extra in the rebar conf as mentioned here http://erlang.2086793.n4.nabble.com/priv-dir-in-escript-td4724193.html but without luck so far. |
It's being looked into! erlang/rebar3#1936 |
zuiderkwast
added a commit
to zuiderkwast/Gradualizer
that referenced
this issue
Nov 11, 2018
This fixes josefs#74, the problem of packaging the priv dir into an escript archive.
zuiderkwast
added a commit
to zuiderkwast/Gradualizer
that referenced
this issue
Nov 11, 2018
This fixes josefs#74, the problem of packaging the priv dir into an escript archive.
Sorry, reopening. I wanted to close the other PR.. |
berbiche
pushed a commit
to berbiche/Gradualizer
that referenced
this issue
Feb 9, 2021
Use erl_prim_loader to get our prelude file using the same mechanism as the code server. An exception is when the file cover compiled. Then we load it from the source code, assuming it is in the same directory as the source of the current module. Thus, cover compiled prelude when running as an escript archive doesn't work but we can live with that. Fixes josefs#74.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When gradualizer is run as an escript (as on travis) it crashes with the below error:
This can probably have something to do with
code:priv_dir(gradualizer) => "/home/travis/build/josefs/Gradualizer/gradualizer/gradualizer/priv"
because it is running from an escript archive.(https://travis-ci.com/josefs/Gradualizer/jobs/156473749)
The text was updated successfully, but these errors were encountered: