Hello all,

I am nearing the end of the driver development and am crossing t's and dotting i's. When running 'make distcheck-light' I am getting a very large number of messages like the following:

While in /nut/docs/man:
  DOC-MAN  Generating nut.conf.5
<unknown>:1: SyntaxWarning: invalid escape sequence '\S'
<unknown>:1: SyntaxWarning: invalid escape sequence '\S'
  DOC-MAN  Generating ups.conf.5
<unknown>:1: SyntaxWarning: invalid escape sequence '\S'
<unknown>:1: SyntaxWarning: invalid escape sequence '\S'
  DOC-MAN  Generating upsd.conf.5
<unknown>:1: SyntaxWarning: invalid escape sequence '\S'
<unknown>:1: SyntaxWarning: invalid escape sequence '\S'
  DOC-MAN  Generating upsd.users.5
<unknown>:1: SyntaxWarning: invalid escape sequence '\S'
<unknown>:1: SyntaxWarning: invalid escape sequence '\S'
(etc.)

Or in /nut/nut-2.8.2.1968.10/_build/sub/docs/man (basically, the same list of files):

  DOC-MAN-HTML Generating nut.conf.html
<unknown>:1: SyntaxWarning: invalid escape sequence '\S'
<unknown>:1: SyntaxWarning: invalid escape sequence '\S'
  DOC-MAN-HTML Generating ups.conf.html
<unknown>:1: SyntaxWarning: invalid escape sequence '\S'
<unknown>:1: SyntaxWarning: invalid escape sequence '\S'
  DOC-MAN-HTML Generating upsd.conf.html
<unknown>:1: SyntaxWarning: invalid escape sequence '\S'
<unknown>:1: SyntaxWarning: invalid escape sequence '\S'
(etc.)

To the best of my knowledge I have not touched the long list of files being processed (except for the new .txt file for the new driver).

Regarding documentation, I have place a new .txt file in  nut/docs/man and updated Makefile.am in SRC_SERIAL_PAGES, MAN_SERIAL_PAGES, HTML_SERIAL_MANS, SrC_USB_LIBUSB_PAGES, and HTML_USB_LIBUSB_MANS.

Are there other sections of the Makefile.am or other files that need to be modified for the man pages to be populated?

Many thanks,

Bill



Virus-free.www.avg.com
_______________________________________________
Nut-upsdev mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev

Reply via email to