similar to: Problems with troff on new installation....

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

----- KSR[T] Website : http://www.dec.net/ksrt E-mail: ksrt@dec.net ----- KSR[T] Advisory #004 Date: Oct 6, 1997 ID

Hi. I am currently running 6.0 (here is uname -a). FreeBSD pc-racine1.mcmaster.ca 6.0-RELEASE-p2 FreeBSD 6.0-RELEASE-p2 #7: Thu Jan 12 09:30:38 EST 2006 root@pc-racine1.mcmaster.ca:/usr/obj/usr/src/sys/OPTIPLEX i386 Just tried a fresh cvsup from cvsup9, a standard compile via cvsup -g -L 2 /usr/share/examples/cvsup/current-supfile && cd /usr/obj && chflags -R noschg *

Hi, I've been cvsupping and trying to buildworld for close to 18 hours now, on and off, with the same result. My current system is: FreeBSD gurney.reilly.home 4.8-STABLE FreeBSD 4.8-STABLE #25: Sat Apr 12 11:56:29 EST 2003 root@gurney.reilly.home:/usr_plus/obj/usr_plus/src/sys/GURNEY i386 About a week old. I've just cvsupped again, and tried a make buildworld, and get the

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 After 3 release candidates, it's finally done - libX11 1.4 is released. As previously warned, libX11 1.4 *requires* libxcb. The Xlib 1.3 branch continues to support the --without-xcb option for the benefit of any remaining distributors who do not yet ship XCB in their stable releases. Changes since the last release candidate: Alan Coopersmith

Aaron Gray wrote: > Turns out I did not have Perl installed and hence no pod2man command, so > it was not groff after all. > > But 'true', what ever it does, does not seem to be working on Cygwin. > > true pod2man --release=1.5 --center="LLVM Command Guide" > /usr/build/llvm/../../src/llvm-1.5/docs/CommandGuide/analyze.pod >

Yeah, that's exactly right, Aaron. "true" is a command that simply returns with an exit status of 0 and ignores its arguments. When pod2man can't be found we define the variable that specifies its path as "true pod2man". This allows the command that should have been run to be shown while at the same time not interrupting the makefile with a failure. This is entirely

Hi Folks, I'm wondering if there are people out there who would be interested in what would be involved in developing an interface between R graphics and the 'pic' language. Explanation; 'pic' has been part of the Unix 'troff' typesetting suite since very early days (1970s), and also of the GNU troff: 'groff'. Its function is to act as a preprocessor,

Kurt, if you really want to find out what things an S help file can contain, you must learn some nroff/troff [ maybe use 'groff', the GNU one ]. As always, ultimate documentation is == source. The definition of the S help is in the two files $SPLUS/cmd/help.[nt]r where nr ^= nroff, i.e. ASCII output tr ^= troff i.e. printed output (e.g via Postscript conversion) help.tr

Turns out I did not have Perl installed and hence no pod2man command, so it was not groff after all. But 'true', what ever it does, does not seem to be working on Cygwin. true pod2man --release=1.5 --center="LLVM Command Guide" /usr/build/llvm/../../src/llvm-1.5/docs/CommandGuide/analyze.pod /usr/build/llvm/docs/CommandGuide/analyze.1 'true' seems to behaving like a

Aaron, This looks to be exactly the same problem as with the executables. There's probably a space where it shouldn't be. Either that or the CommandGuide directory isn't getting created properly. Reid On Thu, 2005-05-19 at 23:12 +0100, Aaron Gray wrote: > Here it is, a missing file "analyze.1" :- > > /usr/bin/groff -Tps -man

For the last few system builds, I've noticed that the variable in /etc/make.conf NO_MAILWRAPPER=true is being ignored, resulting in my sendmail (different than stock version) being overwritten. This applies to 4.8-STABLE; is this a known issue.

Dear Sirs. After Upgrading and installing FreeBSD 5.1-R-p2 from FreeBSD 4.8 (completely fresh installation!) I can not do any manpages and can not do a make world anymore. Man pages would work when setting up an exported environment variable export GROFF_FONT_PATH=/usr/share/groff_font export GROFF_TMAC_PATH=/usr/share/tmac and appropriate in csh. I searched the mailing list and found a lot

I couldn't compile any thing after upgrading 4.6.2 to 4.8 via cvsup I also updated ports via cvsup And nothing would compile, nothing, just error after error I cd /usr/ports did a -"make clean"- (which takes over an hour on my machine) Now all my compile problems have gone away I think I will cd to /usr/ports after doing anything with cvsup or any install, just in case or am I

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

I have FreeBSD-6.1 and it appears the default installation has a full complement of Kerberos5. But, /usr/src/kerberos5/README states: This subtree is world-exportable, as it does not contain any cryptographic code. At the time of writing, it did not even contain source code, only Makefiles and headers. Please maintain this "exportable" status quo. Thanks!

Here it is, a missing file "analyze.1" :- /usr/bin/groff -Tps -man /usr/build/llvm/docs/CommandGuide/analyze.1 > /usr/buil d/llvm/docs/CommandGuide/analyze.ps troff: fatal error: can't open `/usr/build/llvm/docs/CommandGuide/analyze.1': No such file or directory make[2]: *** [/usr/build/llvm/docs/CommandGuide/analyze.ps] Error 1 make[2]: Leaving directory

Hello Mike, i got these error when i`m tried to cvsup my box (4.7 STABLE) to 4.8, these error showed up in the make buildworld step, at stage 4: populating /usr/obj/usr/src/i386/usr/include. and this is my supfile: *default host=cvsup12.FreeBSD.org *default base=/usr/local/etc/cvsup *default prefix=/usr *default release=cvs *default tag=RELENG_4 *default delete use-rel-suffix *default

Hi there, When I do a make buildworld and try to do a make release it will fail telling that it needs the CVSROOT directory. I do cvsup /etc/cvs-supfile and receive nothing ; # /etc/cvs-supfile *default host=cvsup3.nl.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_4_8 *default delete use-rel-suffix *default compress cvsroot-all If I remove