[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #44707] grog(1) (1.22.3 - Solaris 10 X86_64) reports ".../grog/subs

From: anonymous
Subject: [bug #44707] grog(1) (1.22.3 - Solaris 10 X86_64) reports ".../grog/subs.pl 397: Unknown file name extension ..."
Date: Fri, 03 Apr 2015 00:56:27 +0000
User-agent: Mozilla/5.0 (X11; SunOS i86pc; rv:29.0) Gecko/20100101 Firefox/29.0


                 Summary: grog(1) (1.22.3 - Solaris 10 X86_64) reports
".../grog/subs.pl 397: Unknown file name extension ..."
                 Project: GNU troff
            Submitted by: None
            Submitted on: Fri 03 Apr 2015 12:56:26 AM UTC
                Severity: 3 - Normal
              Item Group: Incorrect behaviour
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None




I'm using groff-1.22.3 on a Solaris 10 (X86_64) system and noticed
that grog(1) reports ".../grog/subs.pl 397: Unknown file name
extension ..." in some cases.

For the record, I thought I would document these cases.

>From /usr/share/man, 144 cases like the following:

  Unknown file name extension /usr/share/man/man5/abort.5sql

Given that Solaris 10 has 106 separate man<sect> directories, it
probably a bug that .5sql pages (from the Sun delivered postgres) are
not in the man5sql subdirectory (but a postgres local build does
exactly the same thing).  And given no complaints for all the other
system manual pages, I'm guessing this mismatch in section names is
the cause of the warning.

Locally we compile Free, Libre, and Open Source Software with a unique
prefix for each product instance
(e.g. /pkgs/64-bit/release/<product>-<version>)

I was beginning to think while reviewing the grog(1) output for FLOSS
packages, that the warning was generated when man<sect>/<name>.<sect>
had mismatching <sect> components.

But then the following paths also report the same issue:


But all the system (/usr/share/man) section 1m pages don't give this
message. So I'm unsure why I'm getting this message.

Looking at the code, handle_file_ext() seems to about issuing warnings
and making assignments to $tmac_ext. But the list of valid manual
pages extensions in the code is incredibly small.

On Solaris 10 & 11, /usr/share/man/man.cf lists the manual page
extensions presumably in search preference order. See the example
contents of this file at the end of this message, each MANSECTS= entry
is a single line comma separated value list.

I'm happy to get this message for files in the manual page trees that
are not valid manual pages, and in the FLOSS tree there are few
mistakes. But I'm at a loss as to why, for example, otherwise
seemingly valid manual pages generate this warning. Enlightenment

Peter Bray
Sydney, Australia

On Solaris 10 Update 11, /usr/share/man/man.cf's MANSECT contains 110


On Solaris 11 Update 2, /usr/share/man/man.cf's MANSECT contains 145 entries:



Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]