libtool: Reporting bugs

1 
1 14.2 Reporting bugs
1 ===================
1 
1 If you think you have discovered a bug in libtool, you should think
1 twice: the libtool maintainer is notorious for passing the buck (or
1 maybe that should be "passing the bug").  Libtool was invented to fix
1 known deficiencies in shared library implementations, so, in a way, most
1 of the bugs in libtool are actually bugs in other operating systems.
1 However, the libtool maintainer would definitely be happy to add support
1 for somebody else's buggy operating system.  [I wish there was a good
1 way to do winking smiley-faces in Texinfo.]
1 
1    Genuine bugs in libtool include problems with shell script
11 portability, documentation errors, and failures in the test suite (⇒
 Libtool test suite).
1 
1    First, check the documentation and help screens to make sure that the
1 behaviour you think is a problem is not already mentioned as a feature.
1 
11    Then, you should read the Emacs guide to reporting bugs (⇒
 Reporting Bugs (emacs)Bugs.).  Some of the details listed there are
1 specific to Emacs, but the principle behind them is a general one.
1 
1    Finally, send a bug report to the Libtool bug reporting address
1 <bug-libtool@gnu.org> with any appropriate _facts_, such as test suite
1 output (⇒When tests fail), all the details needed to reproduce
1 the bug, and a brief description of why you think the behaviour is a
1 bug.  Be sure to include the word "libtool" in the subject line, as well
1 as the version number you are using (which can be found by typing
1 'libtool --version').
1