similar to: manpage/groff failure, build world failure (noc 'ascii' device)

Dear Sirs. It seems to me a never ending story. We run a box with a TYAN Thunder 2500 Dual SMP mainboard, 2GB ECC Tyan certified memory, AMI Enterprise 1600 RAID adapter and additional Intel 1000/Pro server type (64 bit) GBit LAN NIC. With FreeBSD 4.8 this was stable, but to achive this state was really hard! It is a story similar to that what happend when we changed towards FreeBSD

Seems something grew beyond what will fit on the kernel floppy. From today's cvsup: linking BOOTMFS text data bss dec hex filename 2659952 210228 208148 3078328 2ef8b8 BOOTMFS -------------------------------------------------------------- >>> Kernel build for BOOTMFS completed on Wed Aug 20 19:03:49 GMT 2003

I tried rebuilding yesterday. It failed [I don't recall the output]. I then completely deleted the /usr/src and /usr/obj, and cvsuped again last night [Approx 7PM on 2003-06-23]. I set the machine up with a buildworld and went to bed. This am I looked at the nohup.out file that was generated and it had failed. I took out the NOMAN=false in /etc/make.conf - as it appeared the failure

I'm trying to build nanobsd. I get the error below. Any ideas? ------------------------------------------------------------- >>> stage 4.2: building libraries -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/nanobsd.soekris/ MACHINE_ARCH=i386 MACHINE=i386 CPUTYPE=

Curious here, What does that mean. Thanks -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Christopher Dobbs Sent: Monday, December 13, 2004 8:23 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: [Asterisk-Users] Ethernet Channel Bank (Comming Soon to a NOC NearYou!) My company has

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

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

CentOS Errata and Bugfix Advisory 2011:1484 Upstream details at : http://rhn.redhat.com/errata/RHBA-2011-1484.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 9c7bc4fe2d402ef82579e7959561fd30 groff-1.18.1.1-13.el5.i386.rpm f9ff26291915acd3852afd34fa608c77 groff-gxditview-1.18.1.1-13.el5.i386.rpm

CentOS Errata and Bugfix Advisory 2011:1484 Upstream details at : http://rhn.redhat.com/errata/RHBA-2011-1484.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 1b76433c5d1f114c55aa4747445622d8 groff-1.18.1.1-13.el5.x86_64.rpm fecd73487ddb4848ee5b572926c1b66d groff-gxditview-1.18.1.1-13.el5.x86_64.rpm

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

Hello freebsd-stable, pls anyone help with this probs.. i always failed to cvsup my box.. in the make buildworld (stage 4:: populating /usr/obj/usr/src/i386/usr/include),session always shown these error msgs: cd /usr/src/share/info; /usr/obj/usr/src/make.i386/make buildincludes; /usr/obj/usr/src/make.i386/make installincludes ===> include cd /usr/src/include;

>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.

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, I was trying to rebuild world on a FreeBSD 10 test system, that I had just installed. ZFS root was setup. I let the installation program do all the ZFS setup and configuration. I put root on a 5 disk encrypted raidz array. Besides the installer configuring 5 times the amount of swap space I asked for (asked for 8gb, installer put 8gb on each drive, for 40gb in total.) everything was working

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 >

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

On CentOS 4 I can't view the mailq man page. I installed postfix and removed sendmail. # LANG=en_US man mailq fopen: No such file or directory Cannot open man page /usr/share/man/man1/sendmail.1.gz No manual entry for mailq # zcat /usr/share/man/man1/mailq.postfix.1.gz .so man1/sendmail.1 Solved replacing with ".so man1/sendmail.postfix.1". Has this little typo to be

Hi, Can anybody point me to some articles that discuss how to use the tc-filter? The man page is still not ready on lartc.org Thanks, Leo

Tom, There appears to be a broken link on the online manpage for shorewall.conf http://www.shorewall.net/manpages/shorewall.conf.html " *GEOIPDIR*=[/pathname/] Added in Shorewall 4.5.4. Specifies the pathname of the directory containing the /GeoIP Match/ database. See http://www.shorewall.net/ISOCODES.html. If not specified, the default value is

Just wanted to make sure this issue was registered separately from the overall confusion I'm exploring in another thread, even though I mention this there too. -- Dave Abrahams BoostPro Computing Software Development Training http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost