Follow-up Comment #6, bug #68497 (group groff): At 2026-07-05T04:21:10-0400, garavel wrote: > Follow-up Comment #5, bug #68497 (group groff): >> If I've reasoned correctly about how groff is built on OpenIndiana, >> then groff -mgan >> ...should load groff's man(7) macro package, which _should_ render >> any OpenIndiana man page satisfactorily--albeit not necessarily >> without emitting warnings. GNU troff is a linter, and other troffs >> are not. > > At first sight, groff -mgan now seems to generate proper PostScript > output, as groff -man used to do in the former OpenIndiana releases.
Okay, that's good news.
> This solves my particular problem, but the assertion-violation issue
> remains when groff -man is called.
This is _not_ good news. See below.
>> Please file another ticket if you find groff man(7)'s rendering of
>> OpenIndiana man pages to be unsatisfactory.
>
> I do not use groff to display the OpenIndiana man pages (nroff is
> sufficient for this), but to generate PS/PDF files for the man page of
> a particular software.
Okay. Well, if you spot any other problems with groff, please let us
know!
> Also, on OpenIndiana:
>
> $ groff -mge
>
> displays the error message:
> gtroff: fatal error: cannot open macro file named in '-m' command-line
> argument 'ge': No such file or directory
That's expected. Of full-service macro packages (see groff_tmac(5)),
System V Unix systems like Solaris did not ship Eric Allman's me(7)
package, or late BSD's mdoc(7) package, so the groff build doesn't
generate compatibility wrappers for them.
man(7), mm(7), and ms(7) are the ones for which it does. All originated
in Bell Labs CSRC Unix or, in the case of mm(7), its USG descendant.
> and
>
> $ groff -mgs
>
> followed by Ctrl-D displays nothing.
Also as expected.
>> Can you verify that these files on your system, in
>> "usr/share/lib/tmac/", have the following checksums and sizes?
>> $ cksum openindiana-doctools-0.5.11/*
>> 3899728472 19008 openindiana-doctools-0.5.11/an
>> 562067901 18198 openindiana-doctools-0.5.11/ansun
>> 3784442836 1818 openindiana-doctools-0.5.11/ansun.tbl
>
> Yes, the checksums are identical to these.
Thank you. That's valuable information but also bad news!
It means you're getting an assertion failure from GNU troff in your host
environment using groff 1.24.1 and (one of) these input files, but I am
not. assert(3) is not supposed to have host-dependent behavior, so it
sounds like something deeply weird is going on.
Sounds like I'll have to fire up VirtualBox after all.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68497>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
