Re: How to compile e.g., tip in MXE

[PhilipNienhuis]

John W. Eaton wrote
> On 03/01/2013 01:53 PM, Philip Nienhuis wrote:
> 
>> However I'd like to try to build a "tip" (or recent version) of the
>> default
>> branch. That failed, as no matter what I tried I consistently got the
>> 3.7.2
>> snapshot you made a while ago - it is downloaded quite autonomously by
>> some
>> other command in the MXE tree.
>> I couldn't find where that download is initiated so that I could
>> circumvent
>> it for octave itself. Grepping for "[download]" (one of the repeated
>> messages during an MXE build) didn't help me.
>>
>> (I made a "snapshot" by hg-cloning the default octave branch, doing a
>> ./bootstrap inside, and tar/zipping it. Maybe naive, but it is just a
>> start)
> 
> Make a regular distribution tarball with "make dist".  Then do the same 
> for this new version as you did for 3.6.4.
> <snip>
> The rules that perform the download steps for MXE are in the top-level 
> Makefile.  Search for WGET.

I'm sorry for some n00b questions.

I couldn't find how to invoke "make dist" from a just cloned hg repo. What
do I need to do to get that far? AFAICS I'd need to bootstrap & configure
before a Makefile with "dist" target is present.

As to the MXE build: after running ./bootstrap and copying in some files
(Changelog, AUTHORS, etc., copied from a simultaneous Linux build) and
tarzipping them + copying into mxe-octave/pkg the build goes OK until:

(I've run with " --jobs 2" so I guess a few messages have been mixed up)
:
../../run-octave -f -q -H -p
/home/philip/devel/octdev/mxe/mxe-octave/tmp-octave/octave-3.7.2d/doc/interpreter
--eval "geometryimages ('voronoi', 'eps');"
mv vectorize.texi-t vectorize.texi
../../run-octave -f -q -H -p
/home/philip/devel/octdev/mxe/mxe-octave/tmp-octave/octave-3.7.2d/doc/interpreter
--eval "geometryimages ('triplot', 'eps');"
/home/philip/devel/octdev/mxe/mxe-octave/tmp-octave/octave-3.7.2d/.build/libtool:
line 10095:
/home/philip/devel/octdev/mxe/mxe-octave/tmp-octave/octave-3.7.2d/.build/src/octave:
No such file or directory
make[5]: *** [voronoi.eps] Error 127
make[5]: *** Waiting for unfinished jobs....
/home/philip/devel/octdev/mxe/mxe-octave/tmp-octave/octave-3.7.2d/.build/libtool:
line 10095:
/home/philip/devel/octdev/mxe/mxe-octave/tmp-octave/octave-3.7.2d/.build/src/octave:
No such file or directory
make[5]: *** [triplot.eps] Error 127
make[5]: Leaving directory
`/home/philip/devel/octdev/mxe/mxe-octave/tmp-octave/octave-3.7.2d/.build/doc/interpreter'
make[4]: *** [install-recursive] Error 1
make[4]: Leaving directory
`/home/philip/devel/octdev/mxe/mxe-octave/tmp-octave/octave-3.7.2d/.build/doc'

...which I suppose is due to the file suffixes of octave.exe etc. not
matching what the 'run-octave' command expects - in file
<builddir>/run-octave I see:
octave_executable="$builddir/src/octave"
rather than
octave_executable="$builddir/src/octave.exe"

All four octave binaries
(octave.exe/octave-cli.exe/mkoctfile.exe/octave-config.exe) were built so at
least that looks good, it's a postprocessing step (building the docs) that
fails. 
oct-files weren't made yet (couldn't find them in the tree).

What can I do to get further in the MXE build?

Thanks,

Philip




--
View this message in context: 
http://octave.1599824.n4.nabble.com/How-to-compile-e-g-tip-in-MXE-tp4650405p4650476.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.