Re: Segmentation Fault with Octave MXE under Windows

[ijourneaux]

Philip Nienhuis wrote
> I usually put the .tar.gz into 
> <mxe-octave>
> /pkg by hand. If mxe starts downloading you know you've entered the wrong
> checksum and you can interrupt mxe.
> 
> You'd currently have to edit the checksum + version in src/octave.mk
> (until jwe updates mxe). 
> If you edit src/stable-octave.mk instead you also have to remove the
> various associated patch files - those do not apply cleanly to 3.8.2-rc1.
> (once again: in Mingw do "openssl sha1 octave-
> <version>
> .tar.gz" to get the checksum)

That seemed to work Philip. I was able to compile up Octave 3.8.2

On another note, 3.8.2 doesn't address the two bugs I am butting up against.
Under Windows

1. Segfault after test imread; exit(0);
2. writing to .jpg with imwrite doesn't produce the correct output.

Take Care



--
View this message in context: 
http://octave.1599824.n4.nabble.com/Segmentation-Fault-with-Octave-MXE-under-Windows-tp4664305p4664609.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.