GNU Make on Mac: Still 3.81, and 10 of 17 Fail Silently

Every Mac with the Command Line Tools has GNU make, but it's GNU Make 3.81, released on April 1, 2006. On the Mac mini M4 that runs this blog, macOS 26.4.1 still ships that version at /usr/bin/make. The current release is 4.4.1, from February 2023. The gap is 17 years and five feature releases, and Makefiles written in the last decade use features from those releases.

I wanted to know what happens when one of those Makefiles hits 3.81, so I wrote 17 small Makefiles. Each one uses one feature added in 3.82 or later, and I ran every one through Apple's 3.81 and Homebrew's 4.4.1. Make 3.81 got all 17 wrong. Seven of them stopped with an error. The other ten exited 0 and printed the wrong result, which is the dangerous case. Below are the results, what people on GitHub keep running into, and how to install a current GNU make next to Apple's.

Which make does a Mac have?

$ make --version | head -2
GNU Make 3.81
Copyright (C) 2006  Free Software Foundation, Inc.
$ xcrun -f make
/Library/Developer/CommandLineTools/usr/bin/make
$ ls -l /usr/bin/make
-rwxr-xr-x  78 root  wheel  118928 Apr  6  2026 /usr/bin/make

/usr/bin/make isn't make itself. The link count of 78 shows it's the same 118,928-byte file as /usr/bin/m4, /usr/bin/bison and other developer tools. It's a shim that asks xcrun where the real tool is and runs the 403,216-byte binary inside the Command Line Tools. That's why updating the Command Line Tools never changes the version. Apple installs the same 3.81 every time.

Apple hasn't said why it stopped at 3.81. The license is where the change happened, though. I downloaded both tarballs from ftp.gnu.org: make-3.81/COPYING is GPL version 2, and make-3.82/COPYING is GPL version 3. This is the same split that left macOS with bash 3.2. The same pattern of a familiar name on an old build turned up when I checked the macOS rsync version and sqlite3 on Mac.

17 newer features, run through 3.81

Each probe is a Makefile of two to five lines with a known correct output. "Since" is the version whose GNU make NEWS file introduces the feature. Every probe printed the right output under 4.4.1 and exited as expected.

Feature	Since	What 3.81 did	Exit
.ONESHELL	3.82	cd /tmp then pwd printed the Makefile's directory	0
.SHELLFLAGS = -ec	3.82	false; echo … kept going and printed	0
define X :=	3.82	$(X) expanded to nothing	0
Shortest-stem pattern rules	3.82	Chose the generic %.o rule over lib/%.o	0
X != cmd	4.0	Defined a variable literally named X !	0
$(file >out,…)	4.0	Wrote no file	0
.EXTRA_PREREQS	4.3	The extra prerequisite never ran	0
Grouped targets a b &:	4.3	Ran the recipe twice under -j2	0
$(let …)	4.4	Expanded to nothing	0
$(intcmp …)	4.4	Expanded to nothing	0
undefine	3.82	missing separator	2
.RECIPEPREFIX	3.82	missing separator	2
private modifier	3.82	No rule to make target `private'	2
X ::= value	4.0	No rule to make target `='	2
--output-sync / -O	4.0	invalid option -- O	2
--trace	4.0	unrecognized option `--trace'	2
# inside $(shell …)	4.3	unterminated call to function `shell'	2

The errors are the easy ones, because you see them. The ten silent results are a problem because 3.81 doesn't reject syntax it doesn't know. It reads it as something else that is also valid. A line starting with .ONESHELL: is an ordinary rule for a target with that name, so each recipe line still runs in its own shell. A .SHELLFLAGS assignment just sets an ordinary variable nobody reads. A function 3.81 has never heard of, like $(file …) or $(let …), becomes a reference to an undefined variable and expands to an empty string. X != echo hello parses as a plain = assignment to a variable named X !. You can see it with make -p:

$ printf 'X != echo hello\nall:\n\t@echo "[$(X)] [$(X !)]"\n' > bang.mk
$ /usr/bin/make -f bang.mk
[] [echo hello]
$ gmake -f bang.mk
[hello] []

The .SHELLFLAGS case does the most damage. People set .SHELLFLAGS := -eu -o pipefail -c so that a failing command inside a pipeline fails the recipe (the same problem I wrote up in bash pipe exit codes). On 3.81 that line is ignored, the recipe runs with the default -c, and a failed step can still end with exit 0. Grouped targets fail in a similar way that's easy to miss. A code generator that writes both parser.c and parser.h runs twice in a parallel build, and the second run can overwrite the first one's output while the compiler is reading it.

What people are hitting on GitHub

To check that these are real problems and not only my test cases, I searched GitHub issues and PRs for "GNU Make 3.81" macOS. There were 1,604 matches, and the search API returns at most 1,000, so I pulled the top 999 by relevance on October 11. They come from 722 repositories, and 850 of the 999 were opened in 2026. I then searched each title and body for feature names. A match means the feature is mentioned, not that it was confirmed broken, and I left out != and -O because those patterns also match shell comparisons and other flags.

• .SHELLFLAGS: 73 · .ONESHELL: 57 · $(file …): 28 · grouped targets &:: 14 · .RECIPEPREFIX: 10 · ::=: 7
• 62 mention gmake and 25 mention brew install make as the fix

A few of these show what this looks like in real projects. raylib #5460 reports that != "is not supported on default macos make" and broke web builds of the examples. lazyslice #137 describes the .SHELLFLAGS failure exactly: make install-proof "exited 0 on a failed build on macOS". ruby/ruby #18668 says that with static extensions, a parallel build under 3.81 "silently produces a ruby without any extension or encoding". vunet-dante-combiner #13 is the # case from my last table row: $${v#v} inside $(shell …) starts a comment under 3.81 and swallows the closing parenthesis.

How to install and update GNU make on Mac

You can't replace /usr/bin/make, and you don't need to. Homebrew's formula installs 4.4.1 with a g prefix, so it sits next to Apple's version instead of replacing it:

$ brew install make          # 2.4 s here, 1.3 MB in the Cellar
$ gmake --version | head -1
GNU Make 4.4.1
$ make --version | head -1
GNU Make 3.81                # unchanged
$ export PATH="/opt/homebrew/opt/make/libexec/gnubin:$PATH"
$ make --version | head -1
GNU Make 4.4.1

Like brew install sqlite, installing it doesn't change what make runs. The Homebrew make formula puts an unprefixed make only in libexec/gnubin, and you have to add that directory to PATH yourself, usually in ~/.zshrc. Intel Macs use /usr/local/opt/make/libexec/gnubin. Put it in your shell profile only if you want every make to be 4.4.1. A launchd job, a cron line or an IDE that starts without your profile will still find /usr/bin/make. For those, call gmake by name. A parallel build also needs a job count, which on Apple silicon is trickier than it looks. See nproc on Mac.

Make the Makefile fail loudly instead

If other people run your Makefile on Macs, don't depend on them reading the README. Check the version at the top of the file. GNU make 3.82 and later list their features in .FEATURES, so you can test for the specific feature you rely on:

ifeq ($(filter oneshell,$(.FEATURES)),)
$(error This Makefile needs GNU make 3.82+ (.ONESHELL). Found $(MAKE_VERSION). Try: brew install make, then run gmake)
endif

$ /usr/bin/make -f F2.mk
F2.mk:2: *** This Makefile needs GNU make 3.82+ (.ONESHELL). Found 3.81. Try: brew install make, then run gmake.  Stop.
$ gmake -f F2.mk
/tmp

Under 3.81, .FEATURES contains target-specific order-only second-expansion else-if archives jobserver check-symlink. Under 4.4.1 it adds shortest-stem undefine oneshell nocomment grouped-target extra-prereqs notintermediate shell-export jobserver-fifo output-sync load. A simpler check is $(filter 4.%,$(MAKE_VERSION)), which rejects every 3.x version. Either check turns a silent wrong build into an error you can see.

FAQ

Is GNU make installed on Mac by default?

Yes, once the Command Line Tools are installed. /usr/bin/make is an xcrun shim that runs GNU Make 3.81 from /Library/Developer/CommandLineTools/usr/bin/make. Version 3.81 was released on April 1, 2006, and macOS 26.4.1 still ships it. The current GNU make release is 4.4.1.

How do I update make on a Mac?

Run brew install make. Homebrew installs GNU Make 4.4.1 as gmake and leaves Apple's /usr/bin/make in place. To have the plain make command run 4.4.1, add /opt/homebrew/opt/make/libexec/gnubin (or /usr/local/opt/make/libexec/gnubin on Intel) to the front of PATH. Scripts and launchd jobs that don't load your shell profile should call gmake directly.

Why is the make on macOS so old?

Apple has not explained it, but GNU Make 3.81 is the last release under GPL version 2, and 3.82 (July 2010) moved to GPL version 3. macOS stopped updating bash at 3.2 at the same license boundary. As a result, Makefile features from 3.82 onward, such as .ONESHELL, .SHELLFLAGS, != and grouped targets, are missing or silently misread by the make that ships with macOS.

Method: I ran 17 probe Makefiles (in research/gnu-make-mac-raw/probes, each with its expected output) through /usr/bin/make 3.81 and Homebrew's gmake 4.4.1 on a Mac mini M4 (Mac16,10) running macOS 26.4.1 (25E253) on October 11, 2026. A probe passed only if the exit code and output matched. I took the version a feature was introduced from GNU make's NEWS file and the license versions from the COPYING files in the make-3.81 and make-3.82 tarballs on ftp.gnu.org. The GitHub numbers come from 999 search results (the API's limit) for "GNU Make 3.81" macOS, collected on October 11, 2026. Matches are keyword mentions in titles and bodies, and I didn't verify each report. I didn't test Xcode.app's toolchain, Intel Macs or any macOS version other than 26.4.1.