继续翻译
复制代码
Before reporting a bug or trying to fix it yourself, try to isolate
it to the smallest possible makefile that reproduces the problem. Then
send us the makefile and the exact results `make' gave you, including
any error or warning messages. Please don't paraphrase these messages:
it's best to cut and paste them into your report. When generating this
small makefile, be sure to not use any non-free or unusual tools in
your recipes: you can almost always emulate what such a tool would do
with simple shell commands. Finally, be sure to explain what you
expected to occur; this will help us decide whether the problem was
really in the documentation.
Once you have a precise problem you can report it in one of two ways.
Either send electronic mail to:
bug-make@gnu.org
or use our Web-based project management tool, at:
http://savannah.gnu.org/projects/make/
In addition to the information above, please be careful to include the
version number of `make' you are using. You can get this information
with the command `make --version'. Be sure also to include the type of
machine and operating system you are using. One way to obtain this
information is by looking at the final lines of output from the command
`make --help'.
复制代码
在你报告一个bug，或正打算自己修复它之前，请先把它隔离成更小的 , 仍然出现同样问题的makefile。
然后发送我们这个makefile, 还有整个的make 命令的结果，包括任何的错误和警告信息。
请不要更改这些信息：
最好是剪切/粘贴这些信息到你的报告里。
当创建上述的makefile的时候，
请确保不要在您的指令片段中使用任何非自-由软件，或者其他不常见的工具：你几乎总是可以用简单的shell 命令来模拟此类工具。最后，请确保你需要说明你期待发生什么；这将帮助我们判断是否问题确实存在。
一旦你有了对问题的清晰描述，你可以采取如下两种方式之一来报告之。
发送电子邮件到: bug-make@gnu.org
或者 使用我们的 基于 web的 项目管理工具：
http://savannah.gnu.org/projects/make/
后文待续
本文转自健哥的数据花园博客园博客，原文链接：http://www.cnblogs.com/gaojian/archive/2012/09/12/2681674.html，如需转载请自行联系原作者
