- #Make.exe crashes when installing packages gnu octave Patch
- #Make.exe crashes when installing packages gnu octave code
tmp/ccuq23Lz.s:176: Warning: unknown section attribute 'S' tmp/ccuq23Lz.s:176: Warning: unknown section attribute 'M' tmp/ccuq23Lz.s:174: Error: junk at end of line, first unrecognized character is `,' tmp/ccuq23Lz.s:164: Error: junk at end of line, first unrecognized character is `,' tmp/ccuq23Lz.s:95: Error: junk at end of line, first unrecognized character is `,'
tmp/ccuq23Lz.s:24: Error: junk at end of line, first unrecognized character is `,' tmp/ccuq23Lz.s:18: Error: junk at end of line, first unrecognized character is `b'
tmp/ccuq23Lz.s:17: Error: junk at end of line, first unrecognized character is `b' tmp/ccuq23Lz.s:12: Error: junk at end of line, first unrecognized character is `v' tmp/ccuq23Lz.s:11: Error: junk at end of line, first unrecognized character is `v' tmp/ccuq23Lz.s:7: Error: junk at end of line, first unrecognized character is `p' tmp/ccuq23Lz.s:6: Error: junk at end of line, first unrecognized character is `p' In the mean time I've made cloned a fresh mxe-octave repo and that fails consistently as follows in build-gcc: Thanks, building now gets past isl and ends -apparently, have yet to test- successfully. Maybe it is time to re-attempt a native build on MinGW (using e.g., 4.9.2) to check if the cross-compiler is reliable. IOW, somewhere earlier in the (then) 4.1.0+ branch something happened that hampered building OF packages.
#Make.exe crashes when installing packages gnu octave Patch
OK, gui-release (3.9.0+) was required to build some OF packages but they did run fine in default (the then 4.1.0+) in my dual-version MXE builds ( patch #8469). It must have happened somewhere before the time that gui-release and default were merged a few weeks before that moment these problems didn't occur.
#Make.exe crashes when installing packages gnu octave code
The fact that the same code works well with another compiler version gives a very itchy feeling.Ī while ago I tried to look back in Octave's own log to see when the change happened that provoked these crashes. I've put cout statements after almost every statement in, all variable values thus echoed to the screen look valid, and the next statement (completely valid c++ syntax) crashes the application. I do not fully trust the gcc compiler(s - both cross and cross-built native). On my Linux system (Mageia-4) that build goes straight trough, so maybe there is an incompatibility problem on the Ubuntu side (note: I don't say "bug"). As to bug #45039, AFAIU that refers to the host's build chain (Linux gcc) that is used to build the cross-compiler.