similar to: Man pages

Hi, On systems that have mandoc installed but are missing an nroff binary, the configure script will fall back to pre-formatted manual pages despite the fact that mandoc could be used. The proposed patch adds mandoc as a valid formatter to configure.ac. As mandoc supports the -mdoc flag, it can simply be added to the list of nroff-like binaries. Wolfgang -------------- next part --------------

HPUX doesn't seem to ship with a set of troff macros that can handle the OpenSSH manpages. Maybe other OSs have this problem? Rather than sodding about with the tmac/ directory, I think we should do one of two things: 1. Ship a set of preformatted manpages, and either auto-install them in $prefix/man/cat{1,1m} or just have instructions in INSTALL to do so 2. Recommend users install groff

Hi Team, I'm looking to "upgrade" my sites ssh installation from the original. I have built openssh-2.3.0p1 and it looks good. I am puzzled as to why there are so many source distributions? However, that is not why am writing - the man pages provided do not format with either Solaris 'nroff -man' or 'groff -man'. What am I missing here? Thanks for your help. Scott

AIX v4.3 returns the correct error $ /usr/bin/nroff -mdoc a /usr/bin/nroff: 1004-010 Cannot find or open /usr/lib/tmac/tmac.doc $ echo $? 130 $ EdGy

Version info: OpenSSH_7.3p1, OpenSSL 1.0.2i 22 Sep 2016, Arch linux The ssh-agent.1 man page seems to have an indentation oddity, at least, as formatted with recent Arch linux manpage toolset. Here's what appears in the formatted output just after the description of the the "-t" option: ---------- Begin formatted output ------------------------------------- -t life

These are all in the port of 1.2.3pre2: - configure accepts --includedir, but doesn't seem to pass it on to the Makefile. You have to edit the Makefile manually if you have include files anywhere but /usr/include. Which is a problem because... - The Makefile doesn't include /usr/local/include by default, which is where zlib installs itself by default. Probably oughta be in there.

Hi! I'm trying to cross-compile 4.8-STABLE world to install it over NFS later. I have ./make.conf: # start of file CPUTYPE=i486 KERNCONF?=CONS MODULES_WITH_WORLD=true DESTDIR=/mnt/cons # end of file I run: dir=`pwd` make __MAKE_CONF=$dir/make.conf buildworld 2>&1 | tee $dir/bw.log It fails: ===> gnu/usr.bin/groff/contrib ===> gnu/usr.bin/groff/contrib/mm sh

http://bugzilla.mindrot.org/show_bug.cgi?id=550 Summary: Problems with .Ql in mdoc Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: minor Priority: P2 Component: Documentation AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: cjwatson at

Hi, Just tested the latest snapshot on RHL72 via building RPM's of it. Nroff detection was wrong, and if no --with-mantype was specified, the type would always revert to cat. This one-byter fixes it. -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert

Hi, Is there an easy way to "fix" the man pages to work with Solaris. Solaris uses the "an" ie /usr/share/lib/tmac/an nroff macros and I guess openbsd doesnt!! cheers Jim

Dear authors of Vorbis, currently, the manpages that come with vorbistools are written in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters: groff(1) on most Linuxes and mandoc(1) on

Why would this be happening, and how can I fix this - the man subsystem hasn't been working because of this for a while. This is FreeBSD-4.9-Prerelease: # gdb man man GNU gdb 4.18 (FreeBSD) This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols found)... /usr/share/tmac/man: No such file or directory. And when I go to run a manpage, I sometimes get this

Hi The man pages don't format properly on Tru64 unix for portable openssh. They come out as a solid lump of text. I managed to fix the problem by including the line .so /usr/local/share/groff/tmac/tmac.andoc (I have GNU groff installed) In the man pages. It appears the OSF -man option on nroff doesn't format the pages correctly. Thanks Jeremy -- Jeremy Sanders <jss at

Hello, the man pages for openssh-2.3.0p1 look bad on our Tru64 Unix V4.0E systems. (Secure Shell) is a program for logging into a remote machine and for executing commands on a remote machine. It is intended to replace rlogin and rsh, and provide secure encrypted communica- tions between two untrusted hosts over an insecure network. X11 connections and arbitrary TCP/IP ports can also be

On 2016-09-28 00:10, Ingo Schwarze wrote: > The patch also inserts a few needless .PP before .SH, but that does > no harm. mdoc2man.awk is a terrible hack and not a proper parser > in the first place, so we shouldn't expect beauty in its output. > If the output is correct and portable, that's good enough. At some > point, we should replace mdoc2man.awk with mandoc -Tman

Dear authors of NSD, currently, the manpages that come with NSD are written in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. See a version of nsd-checkzone.8 below as an example. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters:

Dear authors of Opus, currently, the manpages that come with opus-tools are written in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters: groff(1) on most Linuxes and mandoc(1) on the

Guus The mdoc warnings (on FreeBSD 8) are getting a little bit annoying at times: anywi at lcrproxy:/usr/ports/security/tinc/work/tinc-1.0.19/doc % man tinc.conf 2>&1 | head -5 mdoc warning: Empty input line #6 mdoc warning: Empty input line #10 mdoc warning: Empty input line #15 mdoc warning: Empty input line #22 mdoc warning: Empty input line #30 There are hundreds. Ctrl-L refreshes

Pascal Volk writes: >> Cut&pasted off the terminal man page output. Looking into >> man1/doveadm-move.1, I see >> >> .B doveadm move \-u jane Archive/2011/09 mailbox INBOX BEFORE \(rs >> .B 2011-10-01 SINCE 01-Sep-2011 >> >> so it's a problem with my nroff, not dovecot's man pages. (Hmm, it >> happens with groff too -- it appears

On Thu, 3 May 2001, Gus Mancuso wrote: I haven't seen the answer to this question (included way below) yet. I'm installing it on Solaris 8 and have the same problem - I can't read the man pages in any format other than 80 column wrapped text. The Solaris 8 is pretty generic, with all the current patches. OpenSSH version is 2.9p1. The man pages stored in /usr/local/man/manx are