Created attachment 1205382 [details] rebar output Description of problem: I've been working on debugging ejabberd's build, and I think it might be a problem in rebar. It looks like rebar is checking the dependencies and exiting with code 0 with seemingly no errors, without building anything. Version-Release number of selected component (if applicable): erlang-rebar-2.6.4-2.fc26.x86_64 How reproducible: Every time Steps to Reproduce: 1. Try to build ejabberd on Rawhide Actual results: The build fails, due to rebar not building any beam or app files. Expected results: Rebar should either build the files or print an error and return an exit code. Additional info: I am going to attach the full rebar output. I used my spec file to create a failing build in ~/rpbbuild/BUILD/ejabberd-16.08 so that I would have all the patches applied and dependencies installed. Then I ran the commands shown in the attachment. Note that rebar exits after resolving the dependency information, but does not seem to build any output, doesn't print errors, and returns a 0 exit code. The output does not show this, but earlier in this shell session I did run these commands so that rebar would skip looking for the dependencies in the deps/ folder: REBAR_DEPS_PREFER_LIBS=TRUE export REBAR_DEPS_PREFER_LIBS IGNORE_MISSING_DEPS=TRUE export IGNORE_MISSING_DEPS
Peter got ejabberd to build by avoiding their Makefile. I'm still not sure why rebar wouldn't build as described here, but I'm happy to assume that it was an environmental problem. Since I'm unblocked, I will close this for now.