[erlang-questions] Erlang/OTP 21.0-rc1 (Release Candidate)

Kostis Sagonas kostis@REDACTED
Fri May 4 19:21:05 CEST 2018


On 05/04/2018 04:58 PM, Andreas Schultz wrote:
> Hi,
> 
> The RC breaks rebar3 badly, not sure if it's rebar's fault or a problem 
> with the new logger...
> 
> With an up to date rebar3 clone:
> 
>      rebar3$ ./bootstrap
>    (no logger present) unexpected logger message: {log,error,"Error in 
> process ~p with exit 
> value:~n~p~n",[<0.39.0>,{badarg,[{ets,lookup,[logger,proc_lib],[]},{logger_config,allow,3,[{file,"logger_config.erl"},{line,42}]},{proc_lib,crash_report,4,[{file,"proc_lib.erl"},{line,508}]},{proc_lib,exit_p,3,[{file,"proc_lib.erl"},{line,269}]}]}],#{error_logger=>#{emulator=>true,tag=>error},gl=><0.37.0>,pid=><0.39.0>,time=>-576460751953591}}
>    (no logger present) unexpected logger message: {log,error,"Error in 
> process ~p with exit 
> value:~n~p~n",[<0.39.0>,{badarg,[{ets,lookup,[logger,proc_lib],[]},{logger_config,allow,3,[{file,"logger_config.erl"},{line,42}]},{proc_lib,crash_report,4,[{file,"proc_lib.erl"},{line,508}]},{proc_lib,exit_p,3,[{file,"proc_lib.erl"},{line,269}]}]}],#{error_logger=>#{emulator=>true,tag=>error},gl=><0.37.0>,pid=><0.39.0>,time=>-576460751953591}}
>     ...
> 
> And so on...

FWIW, I experienced this problem last Friday when I updated my copy of 
OTP's 'master' branch, and built starting from a 'make clean'.  These 
errors were there with me all the time.  Note that this has nothing to 
do with 'rebar*'.  I was just trying to run the HiPE tests with ct_run.

Then I spent about two hours investigating what the issue could be and 
did not really get anywhere.  Then I tried a clean git checkout of OTP 
and that built a version that did not spit any such errors.  Turns out 
that this issue can also be fixed by just zapping all generated files 
under 'bin' and then re-building everything:

	cd otp
	/bin/rm -r bin
	git checkout -- bin

	./otp_build autoconf ; ./configure ... ; make   // build again

[I did not investigate further which exact file under bin was the culprit.]

Perhaps the issue you are facing is similar and can be solved in a 
similar way.

Kostis


PS. A suggestion to the OTP folks:

If there is no intention of fixing the 'make clean' target to work 
properly, why don't you just remove it so that there is less confusion?



More information about the erlang-questions mailing list