Re: Segmentation Fault with Octave MXE under Windows

[Philip Nienhuis]

ijourneaux wrote
> 
> Philip Nienhuis wrote
>> That tmp-
>> <package>
>>  file is overwritten for each rebuilt package on each mxe build of
>> Octave.
>> Do you cross-compile (on Linux) or build natively (on Windows)?
> I am cross-compiling.
> Philip Nienhuis wrote
>> With an MXE build (native and cross-), you feed a complete Octave
>> "distribution" to mxe (see my previous post in this thread), which will
>> configure/build/install it somewhere internally; afterward the files are
>> copied into a temp dir from where the archive or installer is made.
>> So that means that you won't see individual files being rebuilt - mxe
>> just builds Octave completely from scratch each time.
> If I understand your previous post, the octave source is supplied as a
> package in the MXE-Octave folder tree. From there is is extracted and
> compiled. If I am on the correct page, if you want to edit the source,
> before you compile, you need to edit it in the octave...tar.gz file

Exactly.
+ update the checksum etc. See my previous post in this thread where I
outlined the workflow.

Yeah it is still a bit clumsy currently. Other devs also mentioned this
occasionally. But compared to what is was before on MinGW, it is an enormous
improvement.

I hope native building with MXE will be less troublesome (and slow) someday.
Maybe it already is, but I have no opportunity / priority / time to test
right now. IIRC a native build took > 20-24 hours. I can't assign my boxes
to one task for so long.

Philip




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