make: Bugs

1 
1 1.2 Problems and Bugs
1 =====================
1 
1 If you have problems with GNU 'make' or think you've found a bug, please
1 report it to the developers; we cannot promise to do anything but we
1 might well want to fix it.
1 
1    Before reporting a bug, make sure you've actually found a real bug.
1 Carefully reread the documentation and see if it really says you can do
1 what you're trying to do.  If it's not clear whether you should be able
1 to do something or not, report that too; it's a bug in the
1 documentation!
1 
1    Before reporting a bug or trying to fix it yourself, try to isolate
1 it to the smallest possible makefile that reproduces the problem.  Then
1 send us the makefile and the exact results 'make' gave you, including
1 any error or warning messages.  Please don't paraphrase these messages:
1 it's best to cut and paste them into your report.  When generating this
1 small makefile, be sure to not use any non-free or unusual tools in your
1 recipes: you can almost always emulate what such a tool would do with
1 simple shell commands.  Finally, be sure to explain what you expected to
1 occur; this will help us decide whether the problem was really in the
1 documentation.
1 
1    Once you have a precise problem you can report it in one of two ways.
1 Either send electronic mail to:
1 
1          bug-make@gnu.org
1 
1 or use our Web-based project management tool, at:
1 
1          http://savannah.gnu.org/projects/make/
1 
1 In addition to the information above, please be careful to include the
1 version number of 'make' you are using.  You can get this information
1 with the command 'make --version'.  Be sure also to include the type of
1 machine and operating system you are using.  One way to obtain this
1 information is by looking at the final lines of output from the command
1 'make --help'.
1