Log message:
Do not raise stack limits during the build. It messes up ressource
limits for multi-threaded applications. Bump revision.

Log message:
Readd two forgotten patches.

Log message:
Revert GNU make to 4.1 due to problems in the new job server code.

Log message:
Disable use of new pselect code. At least on NetBSD 7 bulk builds, it
is often resulting in hanging builds by gmake not wait(3)ing for its
children and issues new jobs. Bump revision.

Log message:
Bump PKGREVISION for perl-5.24.0 for everything mentioning perl.

Log message:
Updated gmake to 4.2.1.

Version 4.2.1 (10 Jun 2016)

A complete list of bugs fixed in this version is available here:

http://sv.gnu.org/bugs/index.php?group=make&report_id=111&fix_release_id=107&set=custom

This release is a bug-fix release.

Log message:
Update gmake to 4.2 (again), this time with an upstream patch

The patch fixes the firefox build issue:

From 4762480ae9cb8df4878286411f178d32db14eff0 Mon Sep 17 00:00:00 2001
From: Paul Smith <psmith@gnu.org>
Date: Tue, 31 May 2016 06:56:51 +0000
Subject: [SV 47995] Ensure forced double-colon rules work with -j.

The fix for SV 44742 had a side-effect that some double-colon targets
were skipped.  This happens because the "considered" facility assumed
that all targets would be visited on each walk through the dependency
graph: we used a bit for considered and toggled it on each pass; if
we didn't walk the entire graph on every pass the bit would get out
of sync.  The new behavior after SV 44742 might return early without
walking the entire graph.  To fix this I changed the considered value
to an integer which is monotonically increasing: it is then never
possible to incorrectly determine that a previous pass through the
graph already considered the current target.

Log message:
back out recent gmake 4.2 update due to mozilla products fallout

ok wiz@

Log message:
Revert r1.95 (Mark bin/gmake as not safe for Pax)

Checking again, I cannot reproduce the crashes anymore.

Log message:
Mark bin/gmake from devel/gmake as not safe for Pax {ASLR,MPROTECT}

I observed crashes on NetBSD/amd64 without both options enabled; further
investigation is welcome.