[erlang-bugs] R14B02: "make install-docs" fails on Ubuntu 10.04 / 10.10 (using the source tar-ball)

[Boris Mühmer]

The "funny" thing was (this was also true when I wrote about it concerning
the R14B01 release), that adding the path wasn't enough.

My normal procedure for installing from source is:

    1> tar xvf <TARBALL>
    2> cd <SRCDIR>
    3> export LANG=C
    4> export ERL_TOP="`pwd`"
    5> export PATH="$ERL_TOP/bin:$PATH"
    6> ./configure --prefix=<DESTDIR>
    7> ( make all && make install && make docs && make install-docs )
2>&1 | tee log-build.txt

With step 5 the "right" escript should be in the path, but without patching the
makefile/makefie.in "make install-docs" does fail on "my" systems.

Currently I don't understand why "env" fails to locate the right "escript"
from the PATH.

Besides: there is neither an Erlang installation from the Ubuntu repositories
on my systems, nor is another Erlang installation bin-directory in my PATH.


  - boris


2011/3/17 Lukas Larsson <lukas@REDACTED>:
> Hi Boris and Andrew!
>
> Thanks for pointing this out. It has to do with the fact that an old
> version of escript (and in extension the erlang VM) is used to build the
> docs. A workaround for now is to add /your/r14b02/path/bin/ into your
> PATH and then build the docs.
>
> I'm however unsure if the patch you provided will work for us as it
> might not always be true that one would want to use the
> $ERL_TOP/bin/escript emulator to build the docs. I'll try to come up
> with a solutions which works for both scenarios.
>
> Lukas
>
> On Wed, 2011-03-16 at 14:15 -0400, Andrew Thompson wrote:
>> On Wed, Mar 16, 2011 at 04:51:00PM +0100, Boris M??hmer wrote:
>> > "make install-docs" fails on Ubuntu 10.04 / 10.10 systems using the
>> > R14B02 source tar-ball (like in "R14B01").
>> >
>> > The simple fix for "$ERL_TOP/Makefile.in" (or "$ERL_TOP/Makefile")
>> > would be to change line 412 from
>> >         $(ERL_TOP)/lib/erl_docgen/priv/bin/xref_mod_app.escript
>> > -topdir $(ERL_TOP) -outfile $(ERL_TOP)/make/$(TARGET)/mod2app.xml
>> > to
>> >         $(ERL_TOP)/bin/escript
>> > $(ERL_TOP)/lib/erl_docgen/priv/bin/xref_mod_app.escript -topdir
>> > $(ERL_TOP) -outfile $(ERL_TOP)/make/$(TARGET)/mod2app.xml
>> >
>>
>> Came here to report this. Boris' fix seems to solve the issue but then I
>> get this error:
>>
>> === Entering application common_test
>> make  RELEASE_PATH=/usr/local/lib/erlang   release_docs_spec
>> escript
>> /Users/andrew/otp_src_R14B02/lib/erl_docgen/priv/bin/xml_from_edoc.escript
>> -preprocess true -i /include \
>>               -i ../../../test_server/include -i  ../../include \
>>               -i ../../../../erts/lib/kernel/include -i
>> ../../../../lib/kernel/include \
>>               -i ../../../../erts/lib/snmp/include -i ../../../../lib/snmp/include
>> ../../src/ct.erl
>> escript: exception error: undefined function edoc:file/2
>>   in function  erl_eval:local_func/5
>>   in call from escript:interpret/4
>>   in call from escript:start/1
>>   in call from init:start_it/1
>>   in call from init:start_em/1
>> make[5]: *** [ct.xml] Error 127
>> make[4]: *** [release_docs] Error 2
>> make[3]: *** [release_docs] Error 2
>> make[2]: *** [release_docs] Error 2
>> make[1]: *** [release_docs] Error 2
>> make: *** [install-docs] Error 2
>>
>> Looks like a similar problem, except that this escript is being invoked
>> via 'escript' Changing 'escript' in the Makefile to '$(OTP_TOP)/escript'
>> seems to fix it, but its wrong in a bunch of the doc Makefiles.
>>
>> Andrew
>>
>> ________________________________________________________________
>> erlang-bugs (at) erlang.org mailing list.
>> See http://www.erlang.org/faq.html
>> To unsubscribe; mailto:erlang-bugs-unsubscribe@REDACTED
>
>
>