make is a GNU command, so the only way you can get it on Windows is installing a Windows version like the one provided by GNUWin32. Anyway, there are several options for getting that:

1. Directly download from Make for Windows

2. Using Chocolatey. First, you need to install this package manager. Once installed, you simply need to install make (you may need to run it in an elevated/administrator command prompt):

   choco install make
   

3. Another recommended option is installing a Windows Subsystem for Linux (WSL or WSL 2), so you'll have a Linux distribution of your choice embedded in Windows 10, where you'll be able to install make, gcc, and all the tools you need to build C programs.

4. For older Windows versions (Microsoft Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, or Windows 7 with msvcrt.dll) you can use GnuWin32.

An outdated alternative was MinGW, but the project seems to be abandoned, so it's better to go for one of the previous choices.

What the make install command does depends on how the Makefile is written and what it consists.

The most generic way of finding out what binaries, libraries, man pages, etc. your make command produces so that you can modify your Makefile could be like the one below. I assume you're in the top of your build directory.

touch /tmp/tstamp
make clean
./configure [your options]
make
find . -newer /tmp/tstamp

This should give you a list of files that have been modified since you've created the /tmp/tstamp file.

Compare the list of files being installed with make install with the list obtained by using the find command and add the desired remaining files to your Makefile.

If you get that list and just want to make it work (in a quick and dirty manner), moving them to proper target locations should be a matter of a simple for loop one-liner, bearing in mind the --prefix (if any) you've specified during the build configuration stage.

Make is a general purpose workflow program, usually used for compilation. But it can be used for anything.

When you do something like "make all", the make program executes a rule named "all" from a file in current directory named "Makefile". This rule usually calls the compiler to compile some source code into binaries.

When you do "make install", the make program takes the binaries from the previous step and copies them into some appropriate locations so that they can be accessed. Unlike on Windows, installation just requires copying some libraries and executables and there is no registry requirement as such. In short, "make install" just copies compiled files into appropriate locations.

Run the command:

sudo apt-get install build-essential

Chances are you will need things like gcc to actually do the building so you might as well install those as well. The build-essential package will install other tools used along with make.

To build GNU packages from source the dance is:

./configure --prefix=/usr/local  # Or your preferred place
make
make install

The configure script queries your environment for all sorts of relevant details (compiler version, usability of various language characteristics, various libraries, functions that might carry different names, ...) and creates some header files from the result reflecting the required configuration. It also builds the Makefile. Running make by itself will fail, until you run configure there is no Makefile, and so no install target.

Why do you want that specific version of make? That one is a quite stable package, the announcement doesn't show any revolutionary changes.

A GNU Make source tarball contains a build.sh script to resolve this chicken-and-egg situation. From the README:

If you need to build GNU Make and have no other make program to use, you can use the shell script build.sh instead. To do this, first run configure as described in INSTALL. Then, instead of typing make to build the program, type sh build.sh. This should compile the program in the current directory. Then you will have a Make program that you can use for ./make install, or whatever else.

Yes, they thought of this problem!