[Octave-bug-tracker] [bug #47712] libmng no longer builds under mxe-octave

[Philip Nienhuis]

Update of bug #47712 (project octave):

                  Status:                    None => Confirmed              

    _______________________________________________________

Follow-up Comment #4:

I have reported this (or something very similar) already some time ago (see
a.o.,
https://lists.nongnu.org/archive/html/octave-bug-tracker/2015-05/msg00142.html,
and in earlier postings that I cannot find right now)

It consistently happens with libmng on one of my systems that has a fairly
fast CPU and a fast SSD. Restarting mxe-octave (make nsis-installer) with
JOBS=1 (and still needing to retry several times) allows the build to continue
in the end. When mxe starts building the next package (IIRC: dbus) I interrupt
it and restart with JOBS=5 (or 7, or whatever).

All other packages, incl. octave, build fine with JOBS=5 or 6 or 7 on that
system.

I am fairly sure it is a sort of race condition but I suspect it is related to
disk I/O.
It appears that SSDs are often simply too fast. For example, when Octave
writes files to a zipped/gzipped archive, some delay is required before
accessing that archive to avoid errors. It appears that zip/gzip/etc already
return once the actual disk I/O has been handed to the low-level stuff, but as
that is scheduled using lazy write etc. the actual disk file may come into
existence too late for Octave's next steps. Or maybe it is simply the
directory tree in memory (user memory or system memory, I do not know) that is
updated too late.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47712>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/