[bug #46261] missing usage of EINTRLOOP macro

[Jack Howarth]

Follow-up Comment #11, bug #46261 (project make):

I finally pinned down the actual cause of these regression in parallel builds
on 10.11 with make 4.1 The issue was being triggered by the default usage of
--enable-nls in the build. This drags in a libintl which is built against the
CoreFoundation framework on darwin. The regressions on 10.11 can be either
suppressed by building make 4.1 with the --disable-nls option or rebuilding
gettext using the....

        gt_cv_func_CFPreferencesCopyAppValue=no 
        gt_cv_func_CFLocaleCopyCurrent=no 
        gt_cv_func_CFPreferencesCopyAppValue=no 
        gt_cv_func_CFLocaleCopyCurrent=no

in order to prevent linkage of libintl against the CoreFoundation framework.
This also corresponds with the known behavior of pymol which uses
fork()/exec() under tcl. On darwin, tcl has to be built with
--disable-corefoundation to avoid crashes in pymol. Looking at the
CoreFoundation framework sources, there doesn't appear to be any effort to
handle EINTR error codes on read(), write() and (f)stat() calls.

    _______________________________________________________

Reply to this item at:

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

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