On 23/10/12 04:52, Eli Zaretskii wrote:
>> Date: Mon, 22 Oct 2012 16:18:34 -0700 (PDT)
>> From: LM <lmemsm@...>
>> The FAQ at mingw.org has had a question up for ages about the lack
>> of a man program in the MinGW/msys environment.
Really? Yes, there is an article in the FAQ: far from bemoaning the
lack of a man program, it tells you *how* to read man pages in MinGW;
(the only caveat is that the tools to be used require MSYS).
>> Anyone know the steps to get one building successfully on Windows?
I know of two ways; the easiest, available since Aug-2009:
$ mingw-get update
$ mingw-get msys-man
The second, as documented in that FAQ article, and available since
Mar-2006; (although built as native, this also requires MSYS, and it
likely will not play nicely with MSYS-rxvt nor with MSYS-mintty):
* download, build and install the mingwPORT of groff, (or build
a more recent groff from FSF), using the MinGW/MSYS tools; (I've
recently run into trouble building groff-1.21 this way, but
everything from groff-1.18 through 1.20.1 should build OOTB).
* download, build and install the technology preview package for
man-1.6, from the MinGW package set on SourceForge; this builds
OOTB. (I chose not to provide a pre-built binary of that, not
because it would have been difficult for me, but because it
would have been fiddly for end users to configure, if they'd
chosen to install with a non-default directory organisation).
> Not exactly what you asked for, but there is a 'man' clone here:
> The sources are there, too, and of course they build with MinGW.
While it's good to know about alternatives, such as this, we should not
neglect the offerings from MinGW.org itself, (as noted above).
Just out of curiosity, how does this ezwinport handle the dependencies
of a natively built man? Obviously, the groff/nroff dependency can be
satisfied by an ezwinport of groff, but what about the Bourne Shell
scripted components of the man package, which MinGW.org addresses by