Thank you Walton. On Thu, Apr 30, 2026 at 4:31 AM Jeffrey Walton <[email protected]> wrote:
> On Wed, Apr 29, 2026 at 4:02 PM Pierre Rouleau <[email protected]> > wrote: > > > > On Tue, Apr 28, 2026 at 5:10 PM 胡珂越 <[email protected]> wrote: > >> > >> This is Correct. > >> > >> Keeyou. > >> > >>> If you don't want to build GNU Make by hand, and you are using Homebrew > >>> on your Mac, then just install the latest version of GNU Make that way. > >>> For example: https://formulae.brew.sh/formula/make > > > > As already mentioned, under macOS one alternative is to use Homebrew to > install GNU make. > > > > It might install it as gmake ... > > The binary name should be just 'make' unless it was patched by > someone. See Makefile.am at > <https://cgit.git.savannah.gnu.org/cgit/make.git/tree/Makefile.am#n26>: > > bin_PROGRAMS = make > > Some other GNU programs use something like $(bin_prefix) to add a 'g'. > I think sed and awk use it to name the binary. But that does not > appear to happen with make. (The makefile recipe would use something > like '$(bin_prefix)make', and $(bin_prefix) would be empty or the > letter 'g'). > > > ... but you can either place the Homebrew directory ahead of /usr/bin > > (where Apple old make is located) or create a symlink to the Homebrew > gmake inside another > > of your directories that are placed ahead of /usr/bin in your PATH. > > > > That's what I used under macOS and that works fine. No need to build it > yourself. > > Jeff >
