Re: [mxe-octave] dev branch: build failure in documentation stage? (was Re: [mxe-octave] dev branch: build failure in install stage?)

[Tatsuro MATSUOKA]

> From: John W. Eaton 

> To: Tatsuro MATSUOKA ; Mike Miller ; PhilipNienhuis 
> Cc: "octave-maintainers
> Date: 2016/7/22, Fri 21:34
> Subject: Re: [mxe-octave] dev branch: build failure in documentation stage? 
> (was Re: [mxe-octave] dev branch: build failure in install stage?)
> 
> On 07/21/2016 11:58 PM, Tatsuro MATSUOKA wrote:
>>>  Tatsuro, when you made the archive, did you use the 'make dist' 
> target?
>> 
>>>  Or did you just tar up the contents of the hg working directory after
>>>  running bootstrap? The proper steps to create a source tarball are
>>> 
>>>     ./bootstrap && ./configure && make all && 
> make dist
>>> 
>>>  --
>>>  mike
>> 
>> 
>> 
>>  I did the above.
>>  After "make dist", octave-4.1.0+.tar.gz was generated in build 
> directory.
>> 
>>  The archived file contained the documentation.
>> 
>>  Then I executed mxe-octave using this octave-4.1.0+.tar.gz.
>>  make zip-dist
>> 
>>  Build of default-octave step was stopped.
>> 
>>  /bin/bash run-octave --norc --silent --no-history 
> /home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave/octave-4.1.0+/doc/interpreter/mk_doc_cache.m
>  
> - 
> /home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave/octave-4.1.0+
>  
> /home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave/octave-4.1.0+/doc/interpreter/macros.texi
>  
> libinterp/DOCSTRINGS scripts/DOCSTRINGS > doc/interpreter/doc-cache-t 
> && \
>>  mv doc/interpreter/doc-cache-t doc/interpreter/doc-cache
>> 
> /home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave/octave-4.1.0+/.build/libtool:
>  
> line 11645: 
> /home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave/octave-4.1.0+/.build/src/octave:
>  
> No such file or directory
>>  make[4]: *** [doc/interpreter/doc-cache] Error 127
>>  make[4]: Leaving directory 
> `/home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave/octave-4.1.0+/.build'
>>  make[3]: *** [install-recursive] Error 1
>>  make[3]: Leaving directory 
> `/home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave/octave-4.1.0+/.build'
>>  make[2]: *** [install] Error 2
>>  make[2]: Leaving directory 
> `/home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave/octave-4.1.0+/.build'
>>  make[1]: *** [build-only-default-octave] Error 2
>>  make[1]: Leaving directory 
> `/home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64'
>> 
>>  As you said, run-octave is meaningless because this is cross-build.
>> 
>>  How can I do ?
> 
> The problem is that we now always create the DOCSTRINGS files in the 
> build tree.  So if you are doing a VPATH build from a tarball 
> distribution, new copies will always be created in the build tree even 
> though the files exist and are up to date in the source tree.  So then 
> the DOCSTRINGS files have timestamps that are newer than the doc-cache 
> file and we end up trying to recreate the doc-cache.  That can work for 
> a normal build, but for cross builds it fails.  Rather than trying to 
> play tricks with timestamps or write more files in the source tree, I'm 
> switching to using Perl instead of Octave to build the doc-cache file. 
> I have a patch almost ready to push.
> 
> jwe


jwe

Thank for your very comprehensive explanation.
If you will push the patch, please let us know.

Anyway, using tar ball octave-4.1.0+.tar.gz produced in the source directory 
after make all here,
I could build dev branch source.
At the moment I use source directory build making tar ball for mxe-octave.

Tatsuro