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

[Mike Miller]

On Wed, Jul 20, 2016 at 03:40:34 -0700, PhilipNienhuis wrote:
> tmacchant wrote
> > I then cloned mecurial repo and executed ./bootstrap and archived as
> > octave-4.1.0+.tar.gz
> > and executed make zip-dist.
> > 
> > I have met another error on documentation.
> > 
> > 
> > /bin/bash run-octave --norc --silent --no-history --path
> > /home/tatsuro/work/octave/mxe-octave/mxe-octave-dev-w64/tmp-default-octave/octave-4.1.0+/doc/interpreter/
> > --eval "geometryimages ('doc/interpreter/', 'voronoi', 'txt');"
> > /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/voronoi.txt] 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'
> 
> Yesterday evening I've made a cross-build with the tip (incl. that cset by
> Mike) and that went fine. Maybe limiting the number of make jobs might help?
> (I usually limit it to 2 or 3).
> 
> I have a yet different problem with that same tip but with several
> additional patches (__wglob__, light, ...): 
> in the very latest install stage, libtool complains that it can't find
> .build/src/octave (where I think it wants octave.exe).  Looking at the
> patches involved I can't follow that they'd influence that part of the
> build.  Yet I've seen this before, some years ago.

This is a little disturbing. I wonder if something is being patched
locally that affects the documentation or the images for the manual?

As you know we build the user manual and distribute it with the source
tarball. So if you build from a source tarball none of these steps
should ever be executed.

This is especially bad for cross-building, because the octave
executables that are built are not for the host system, so there is no
way to run octave on the geometryimages function for example.

So the error message above is accurate I think. What I don't know is why
it is trying to build the images at all. I would be interested in
getting a copy of the source tarball and any patches applied that cause
this error.

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