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

[PhilipNienhuis]

tmacchant wrote
> Philip. Sorry I made a mistake to send mail only to you.
> 
>> From: Philip Nienhuis 
>> To: Tatsuro MATSUOKA ; Mike Miller 
>> Cc: "octave-maintainers
>> Date: 2016/7/22, Fri 16:55
>> Subject: Re: [mxe-octave] dev branch: build failure in documentation
>> stage? (was Re: [mxe-octave] dev branch: build failure in install stage?)
>> 
>>T atsuro 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: all in one directory? I usually make dist archives in a separate
>> build 
>> dir as well.
>> 
>> 
> <snip>
>> 
>>>  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 ?
>> 
>> Tatsuro,
>> 
>> Yesterday I successfully built dev Octave tip with mxe, incl. docs.
>> 
>> One thing that I found is that on the Linux side it is seems more
>> reliable for 
>> subsequent mxe-octave cross-builds, to make a complete Linux build in one
>> step.
>> I.e., not having a build, pulling/updating the source tree and then do
>> an 
>> incremental "make".
>> Rather wipe the entire build dir and then do configure && make before 
>> making a dist archive (make all dist).
>> configure && make in an existing build dir doesn't *seem* to be 
>> sufficient - at least for me.
>> 
>> (slightly OT
>> Next thing for me is that once in Windows, Octave can't find its docs
>> (the 
>> docs pane mentions "the info file or compressed version does not 
>> exist".
>> The Start Menu shortcuts to the html and pdf files do work fine, however.
>> Where 
>> are those info or compressed files to be found?)
>> 
>> Philip
>> 
> 
> Philip. Thanks for your suggestion.
> 
> I usually make build directory like "build" and "cd ..../build" and
> ../(octave source dir)/configure ......
> I now try not to make build directory and build in source directory on
> Ubuntu.
> 
> I will report results tomorrow.  

Hopefully Mike can explain if building in source dir is better for later
cross-builds.
For me building in a separate build dir works fine and has mostly worked
fine. 

Best wishes

Philip



--
View this message in context: 
http://octave.1599824.n4.nabble.com/mxe-octave-dev-branch-build-failure-in-install-stage-tp4678650p4678760.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.