Your friend's PC is doing something strange and its not clear from your question what they've done. Your PC is acting normally.
Calling make all Will compile everything, but it doesn't actually make a program called all. It only compiles two programs: hello.exe and add.exe.
So calling ./all should fail because that is asking to run a program called all which doesn't exist.
It's quite possible that your friend has written themselves a program or script called "all". You'll need to ask your friend what that script / program does and how it does it.
Edit
To see what your friend has done open a terminal on your friends pc (like the one in your screen shot) and type the command
ls -lh
This will list all the files in that directory. Look for one named "all". It might look something like this (with the word "all" in green):
-rwxr----- 1 appy appy 67 Oct 23 15:05 all
Assuming that's there you can look at the contents of it by typing
cat ./all
To get yours to work like your friends, create a similar file with the same contents. To make it runnable you may need to change the file permissions:
chmod u+x all
Answer from Philip Couling on Stack OverflowVideos
Your friend's PC is doing something strange and its not clear from your question what they've done. Your PC is acting normally.
Calling make all Will compile everything, but it doesn't actually make a program called all. It only compiles two programs: hello.exe and add.exe.
So calling ./all should fail because that is asking to run a program called all which doesn't exist.
It's quite possible that your friend has written themselves a program or script called "all". You'll need to ask your friend what that script / program does and how it does it.
Edit
To see what your friend has done open a terminal on your friends pc (like the one in your screen shot) and type the command
ls -lh
This will list all the files in that directory. Look for one named "all". It might look something like this (with the word "all" in green):
-rwxr----- 1 appy appy 67 Oct 23 15:05 all
Assuming that's there you can look at the contents of it by typing
cat ./all
To get yours to work like your friends, create a similar file with the same contents. To make it runnable you may need to change the file permissions:
chmod u+x all
"all" in this case is what is called a "pseudo-target" in make terminology. Since there is no build command under the all: ... line, there is nothing that will actually create a file called all (and in fact, having a file in that directory named all and having a timestamp newer than the .c, .o and .exe files is likely to confuse make). The pseudo-target here is simply a way to say that both the other .exe files must be built for make to consider its job done.
Assuming this is GNU Make, an entry .PHONY: all will tell it that all does not really correspond to a file that should exist.
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.
sudo apt-get update
sudo apt-get -y install make
(-y = answer 'yes' to any prompts)
Check the installed version:
make -v