automake-1.16: Reporting Bugs
26.12 Reporting Bugs
====================
Most nontrivial software has bugs. Automake is no exception. We cannot
promise we can or will fix a bug, and we might not even agree that it is
a bug, but we want to hear about problems you encounter. Often we agree
they are bugs and want to fix them.
So, to make it possible for us to fix a bug, please report it. If
you can, though, it is helpful if you check if it is already known. You
can look at the GNU Bug Tracker (https://debbugs.gnu.org/) and the
bug-automake mailing list archives
(https://lists.gnu.org/archive/html/bug-automake/) for previous bug
reports. (We previously used a Gnats database for bug tracking, but it
is no longer online.)
If the bug is not already known, it should be reported. To report
bugs in a way that is useful and efficient, please read How to Report
Bugs Effectively
(https://www.chiark.greenend.org.uk/~sgtatham/bugs.html) and How to Ask
Questions the Smart Way
(http://catb.org/~esr/faqs/smart-questions.html). Good bug reports save
time for everyone.
For a bug report, a feature request or other suggestions, please send
email to <bug-automake@gnu.org>. This will then open a new bug in the
bug tracker (https://debbugs.gnu.org/automake). Be sure to include the
versions of Autoconf and Automake that you use and the kind of system
you’re on. Ideally, post a minimal ‘Makefile.am’ and ‘configure.ac’
that reproduces the problem you encounter. If you have encountered test
suite failures, please attach the ‘test-suite.log’ file.
Info Catalog
automake-1.16: Debugging Make Rules
automake-1.16: FAQ