Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Fri, 17 Mar 2000 11:10:01 -0500 To: Cygwin-general Subject: Re: man pages Message-ID: <20000317111001.D15494@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, Cygwin-general References: <200003170843 DOT TAA15244 AT mustang DOT sdc DOT com DOT au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: <200003170843.TAA15244@mustang.sdc.com.au>; from scldad@sdc.com.au on Fri, Mar 17, 2000 at 07:13:27PM +1030 On Fri, Mar 17, 2000 at 07:13:27PM +1030, Stephen Davies wrote: >I seem to have missed the problem here. > >I built man as one of the first add-ons to both my B19 and B20 setups with >little or no problems. > >All it seemed to need was terminfo, ncurses and groff. Oh, and I think I had >to gzip the man pages themselves. > >Works just fine. > >Thanks again for such a great toolkit. You're welcome. You're right, of course, that man can be compiled and built just like most other UNIX applications. There is nothing magical in B20 which prevents man from working. cgf >"Sean Champ" wrote: >>if you're running b20: how did you even get the manpages to work? >> >>I saw something about it, probably somewhere at cygnus, that suggested >>it wasn't possible to run manpages on b20 -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com