Make: *** No Targets Specified And No Makefile Found. Stop.

The error message “make: *** No targets provided and no makefile found” may appear while you’re working with Ubuntu, Debian, or Red Hat. Stop. Because this is a general problem with GNU Make, you may see it on any number of Unix systems.

A makefile or Makefile does not exist in the current working directory. Fortunately, it’s a simple mistake to correct.

Make: *** No Targets Specified And No Makefile Found. Stop.

Navigating the realm of software development often leads you to a crossroads where tools and utilities like Makefiles become vital.

Understanding the intricacies of Makefiles, from their creation to their execution, can significantly streamline your development process. Let’s demystify the world of Makefiles and dive deep into common errors and their remedies.

What is a Makefile?

A Makefile is a simple way of defining how a program should be compiled and linked. Used with the make utility, it contains a set of rules and dependencies that describe how the program’s source files are interrelated and the commands needed to compile them into executable binaries.

What Causes the “Make: *** No Targets Specified And No Makefile Found. Stop.” Error?

When you encounter this error, make is essentially saying it doesn’t know what to build and can’t find any instructions (a Makefile) to guide it. Common reasons include:

  1. No Makefile in Directory: You might be in the wrong directory or have forgotten to create a Makefile.
  2. Misnamed Makefile: If your Makefile has a different name (like Makefile.txt), make won’t recognize it.

Method 1: A Makefile in the Current Directory Can Be Found Using

It’s possible that you’ll get the same problem if you run make one more time in the current directory. Since your last attempt at running GNU make, you’ve probably opened another terminal session and tried to locate its proper directory, or you’ve used cd.

You may examine what files are in your current directory by running the ls or dir command. Your location in the directory tree may be incorrect. A quick cd command can help ensure that you run make in the correct location if you see directories that should be in your home or root / directory.

Read Also:

  1. BattleFront 2 Mouse Stuck
  2. Windows Doesn’t Have A Network Profile For This Device
  3. A Name Has Not Been Set For This Account. Please Try Again When A Name Has Been Set.

Even if you’re anticipated to be in a specific location, you may find yourself in a different location. Make failed miserably when attempted from the /var/crash directory in our case. The only files in this exact area are from unrelated crash reports, therefore it can’t be expected to execute from there.

Your make command should be executed from a directory somewhere in your home directory, assuming that you haven’t already done so. It’s possible to cd to a directory like /nano-2.9.6 and execute make again, for example, if you’re building the newest version of GNU nano from source.

Make sure there is a makefile in the directory before trying to make it. Remember that you must first configure the installation before you can proceed. The GNU compiler thrives in the ideal environment provided by the configure command. ./configure and the make command can help if you can’t find a makefile, even though you’ve checked in the correct project directory.

Install your project with sudo make install if this compiles well, but remember that you don’t want to build anything as root, so you’ll never want to do sudo make or anything else outside of installation.

Method 2: A Custom Makefile can be Specified

No further action is required if the problem has been resolved. However, if the prior solution didn’t solve your problem, there are two unique scenarios to consider. Writing your own makefile for a project that you’ve been configuring by hand is required for both of these examples.

Using the -f option, you can designate a makefile with a different name than makefile. It is possible to use the command line to specify a backup file, such as makefile.bak, if you have one.

There is no need to use makefile.bak if you don’t wish to ignore mistakes in a custom or old makefile throughout the compilation process. This is generally discouraged, as you’ll likely need to make changes to your makefile if there is a problem with it.

Case sensitivity is another use case that is very closely related to this one. In Unix, each of the following is a separate file:

  • Makefile
  • makefile
  • makeFile
  • MakeFile
  • MakefilE

Packages that have been customised may not be able to read a makefile that uses standard capitalization. Using the -i option, you may ensure that GNU make is able to locate the makefile even if it was handwritten for a coding mission you’re working on.

Take into account the fact that even though your code is complete, you can still run./configure from your own job to ensure that your environment is set up correctly and avoid this issue.

How Do I Stop the “No Rule to Make Target” Error?

This error arises when make can’t find a rule in the Makefile that matches a target or dependency. To fix it:

  1. Check Typing Errors: Ensure that the target’s name in the Makefile matches the name you provided.
  2. Update Dependencies: If a file has been renamed or removed, update the Makefile accordingly.

How Do I Create a Specific Makefile?

Creating a Makefile requires understanding your project’s structure and dependencies. Here’s a simple process:

  1. Open a Text Editor: Create a new file named Makefile.
  2. Define Targets: A target typically represents an output, like an executable.
  3. Specify Dependencies: List the files needed to create the target.
  4. List Commands: Provide the commands to produce the target from its dependencies.

For a basic C program:

my_program: main.c utility.c
gcc -o my_program main.c utility.c

How Do I Run a Target Makefile?

To run a target from a Makefile:

  1. Open the terminal in the directory containing the Makefile.
  2. Use the command make target_name. For example, make my_program.

What Type of File is a Makefile?

A Makefile is a plaintext file, typically devoid of any file extension. It contains a specific syntax and structure that the make utility understands and uses to automate the build process.

What is a Symbol in a Makefile?

Symbols (or variables) in Makefiles store values that can be reused throughout the file. They make Makefiles more modular and easier to maintain. For instance:

CC = gcc
CFLAGS = -Wall
my_program: main.c utility.c
$(CC) $(CFLAGS) -o my_program main.c utility.c

In the example above, CC stores the compiler’s name, and CFLAGS stores compiler options.

Read Also:

  1. No Man’s Sky Failed To Join Lobby
  2. How To Fix Error 31 Other Network Problem
  3. An Unexpected Error Has Occurred Netge-1000


Makefiles, though seemingly daunting, are potent tools for developers. They offer a systematic and automated approach to building projects, saving time and ensuring consistency.

By understanding their structure, errors, and functionalities, one can seamlessly navigate the complexities of software development.