Windows Installer: Difference between revisions

Jump to navigation Jump to search
768 bytes added ,  12 December 2015
Line 82: Line 82:


====If things go wrong====
====If things go wrong====
It is possible that the build of Octave in step 2 works but that if fails in step 3.  Here are some troubleshooting tips in that case.
It is possible that, for example, the build of Octave in step 2 works but that if fails in step 3.  Here are some troubleshooting tips.
* The source will be left in <mxe-octave build>/tmp-default-octave and it is possible to run "configure && make" in that directory.  A possible causes for build failure is having files in your local build directory that are not listed in the module.mk files; these aren't copied into the dist archive.
* The error message displayed by make is simply the last 10 lines of the log file.  This may truncate the actual error message.
* Sometimes running "make" a second time without changing anything will fix the problem.  In particular, autotools rebuilds some files in the first make which may cause the second make to succeed.
* If it is building Octave that failed, the source will be left in <mxe-octave build>/tmp-default-octave and it is possible to run "configure && make" in that directory.
* The configuration will be for the target system, not your own.  In particular, if you have not installed all of the packages that MXE-octave installs, then your configuration will be differentHowever, some configuration variables will differ even if you have the same packages, and some compiler features may be available on the host system that are not available in cross-compile mode.
* A possible causes for build failure is having files in your local source or build directory that are not listed in the module.mk files; these are not copied into the dist archive.


==Installing requirements of MXE Octave==
==Installing requirements of MXE Octave==
122

edits

Navigation menu