Closed slashmili closed 4 months ago
Seems to be fixed in pc v1.15 by #80
I see, the question comes to my mind is why rebar is fetching v1.14.0
? Is there another configuration/version update needs to be done for rebar to get v1.15.0
?
This is the rebar I'm using
rebar3 version
rebar 3.23.0 on Erlang/OTP 27 Erts 15.0
why rebar is fetching v1.14.0 ?
Maybe:
$HOME/.cache/rebar3/hex/hexpm/packages
and finds that there's pc 1.14 already downloaded, and uses that one... why not?If that's your case, some ideas:
rebar3 plugins upgrade --all
{plugins, [{pc, "1.15.0"}]}.
This is my cache dir
$ ls -rf -l $HOME/.cache/rebar3/hex/hexpm/
total 0
drwxr-xr-x 2 milad staff 64 25 Jun 14:50 ./
drwxr-xr-x 4 milad staff 128 13 Jun 10:42 ../
seems like that upgrade command did the trick.
$ rebar3 plugins upgrade --all
===> Fetching pc v1.14.0
===> Analyzing applications...
===> Compiling pc
===> Compiling _build/default/plugins/pc/src/pc_port_env.erl failed
_build/default/plugins/pc/src/pc_port_env.erl:190:10: code:lib_dir/2 is deprecated; this functionality will be removed in a future release
===> Errors loading plugin pc. Run rebar3 with DEBUG=1 set to see errors.
===> Upgrading pc v1.15.0
===> Analyzing applications...
===> Compiling pc
The issue is that I'm using snappyer and in that package, the pc version is not pinned in the plugins settings.
Thanks for the hint!
I noticed that the build is failing on OTP 27
my env:
my
rebar.config
: