make *** no targets specified and no makefile found. stop

by

make takes a makefile as input. Makefile usually is named makefile or Makefile. The configure command should generate a makefile, so that make could be in turn executed. Check if a makefile has been generated under your working directory.

More Related Contents:

  1. What is the purpose of .PHONY in a Makefile?
  2. Creating Makefile with libraries
  3. OS detecting makefile
  4. Recursive wildcards in GNU make?
  5. Define make variable at rule execution time
  6. How to place object files in separate subdirectory
  7. How to generate a Makefile with source in sub-directories using just one makefile
  8. Passing arguments to “make run”
  9. GNU Makefile rule generating a few targets from a single source file
  10. Getting make to create object files in a specific directory
  11. How to write loop in a Makefile?
  12. How to use all *.c files in a directory with the Cmake build system?
  13. What’s the opposite of ‘make install’, i.e. how do you uninstall a library in Linux?
  14. Make: how to continue after a command fails?
  15. How to use LDFLAGS in makefile
  16. Create directories using make file
  17. How to get current relative directory of your Makefile?
  18. How do I check if file exists in Makefile so I can delete it?
  19. Is it possible to set CFLAGS to a linux kernel module Makefile?
  20. How to ensure a target is run before all the other build rules in a makefile?
  21. Best practice for building a make file
  22. Building C-program “out of source tree” with GNU make
  23. What are Makefile.am and Makefile.in?
  24. Run make in each subdirectory
  25. Makefile ifeq logical or
  26. CFLAGS vs CPPFLAGS
  27. CMAKE_MAKE_PROGRAM not found
  28. How do I perform arithmetic in a makefile?
  29. Create a variable in a makefile by reading contents of another file
  30. @ prefix when setting environment variable in Makefile

Leave a Comment