[erlang-bugs] make docs fails in git master

Tuncer Ayaz tuncer.ayaz@REDACTED
Tue Oct 2 16:57:33 CEST 2012


On Tue, Oct 2, 2012 at 4:41 PM, <pan@REDACTED> wrote:
> Nope, daily builds and jenkins show no such symptoms on any of our
> branches.
>
> Maybe you've got some icky erlang in your PATH? Try setting a newly
> built erlang first in the path (as the escript fails).

That's actually how I always build:
$ export ERL_TOP=$PWD
$ export PATH=$ERL_TOP/bin:$PATH
$ ./otp_build setup -a <CONFIGURE_FLAGS>
$ make docs

Same error if I install the build and use PATH=<INSTALL_DIR>/bin:$PATH.

> The make doc should actually take care of this - if there is a built
> escript binary in the tree, it should be used, but it seems not for
> emd2exml. Will look into that. Menawhile, can you confirm that it
> works with a newly built P16 in your path?

P16 == R16?

Same error with OTP_R15B02-616-gaf9a8a0.

> On Sat, 29 Sep 2012, Tuncer Ayaz wrote:
>
>> At least as far back as the R15B02 release 'make docs'
>> in the master branch fails:
>>
>> $ make docs
>> /tmp/otp/master/make/emd2exml /tmp/otp/master/HOWTO/DTRACE.md DTRACE.xml
>> (no error logger present) error: "Error in process <0.3.0>
>> with exit value:
>> {badarg,[{init,request,1,[]},{erl_prim_loader,prim_init,0,[]},
>> {erl_prim_loader,start_it,4,[]}]}
>> "
>> (no error logger present) error: "Error in process <0.2.0>
>> with exit value: {badarg,[{erl_prim_loader,request,1,[]},
>> {init,start_prim_loader,6,[]},{init,do_boot,3,[]}]}
>> "
>> {"init terminating in do_boot",{badarg,[{erl_prim_loader,request,1,[]},
>> {init,start_prim_loader,6,[]},{init,do_boot,3,[]}]}}
>>
>> Crash dump was written to: erl_crash.dump
>> init terminating in do_boot ()
>> make[3]: *** [DTRACE.xml] Error 1
>> make[3]: Leaving directory `/tmp/otp/master/lib/runtime_tools/doc/src'
>> make[2]: *** [docs] Error 2
>> make[2]: Leaving directory `/tmp/otp/master/lib/runtime_tools'
>> make[1]: *** [docs] Error 2
>> make[1]: Leaving directory `/tmp/otp/master/lib'
>> make: *** [docs] Error 2
>>
>> Can anybody else reproduce this?



More information about the erlang-bugs mailing list