From: Jack H. <how...@gm...> - 2016-08-14 18:52:34
|
On Sun, Aug 14, 2016 at 11:48 AM, Jack Howarth <how...@gm...> wrote: > On Sun, Aug 14, 2016 at 10:23 AM, Max Horn <ma...@qu...> wrote: > >> Jack, >> >> > On 12 Aug 2016, at 20:44, Jack Howarth <how...@gm...> >> wrote: >> > >> > Max, >> > It appears to be safe again to re-enable the default nls support in >> the make 4.2.1 build as upstream have fixed the signaling issue.... >> > >> > http://savannah.gnu.org/bugs/index.php?46261#comment12 >> >> That indicates that a change was made which *might* fix the issues that >> troubled make. >> >> But has anybody actually verified that this really does fix the issue? I >> am reluctant to disable the workaround until this is clear -- considering >> that broken builds are much worse than missing nls support. >> >> Max, > Yes. I have been exhaustingly rebuilding all of the previously > problematic packages like openmpi, libgettext8-shlibs and gcc5 with the > newer make 4.2.1 having nls re-enabled on 8 cores. The problem with EINTR > failures has indeed been fixed. > Jack > Also confirmed stability of core 8 builds with nls-enabled make 4.2.1 for the previously problematic builds of cmake, libcurl4, texlive-base and r-base32. > > >> Cheers, >> Max > > > |