Wed 12 Oct 2016 06:13:49 PM UTC, comment #2:
Thanks for the hint! I will now try to compile mxe-octave with "default-octave", this is currently 4.3.0.+, if I'm right this time.
Wouldn't it be a good idea to bump the version in mxe-octave with "stable-octave" to 4.2.0-rc2 now? There is currently no straightforward way to built Octave 4.2.0-rc2 with mxe-octave. (I do know how to do it anyways...)
Feel free to just close this bug report, thanks.
|
Tue 11 Oct 2016 09:06:00 PM UTC, original submission:
I see an error when I use the current mxe-octave to compile stable octave, which is octave-4.2.0-rc2 at the moment.
Here are the details what I do to compile (on Ubuntu 14.04 linux), starting with a recent, fresh and clean copy of the mxe-octave repo (hg id 47051dc285cd):
(To be honest, there is a light change in my copy of the repo: freetype version is updated to 2.6.5. But this shouldn't be the problem, freetype compiles fine.)
Here is the compilation error message from mxe-octave:
And those are the last lines of the "stable-octave" log file:
Is this a known bug (possibly of my elderly OS Ubuntu 14.04) or a new behavior?
Let me know if you need more information on my build system.
(By the way: Why is the subfolder in tmp-stable-octave still named "octave-4.0.3" even if I compile octave-4.2.0-rc2?)
|