I haven't built any tcltk package for a while. I think the last one might 
have been from a scriptics tarball.

I have tcl and tk (and friends) installed as part of Mandrake 8.0 
distribution. When I try to build the tcltk-8.3.3-5mdk.src.rpm package, it 
fails pointing to line 148 of bldmanhelp script. 

        ...etc...
    creating help file tcl/files/gets
    creating help file tcl/files/glob
    creating help file tcl/variables/global
    creating help file tcl/status/history
    creating help file tcl/sockets/http
nroff: broken pipe
    creating help file tcl/control/if
    creating help file tcl/math/incr
    creating help file tcl/status/info
    creating help file tcl/control/interp
Error: Error extracting help from: bldmanhelp.tmp
error writing "file8": broken pipe
    while executing
"puts $nroffFH $matchInfo(line)"
    while executing a match default command
    invoked from within
"scanfile $extractNroffHelpContext $manPageFH"
    (procedure "ExtractNroffHelp" line 25)
    invoked from within
"ExtractNroffHelp $matchInfo(handle) $matchInfo(line)"
    while executing a match command
    invoked from within
"scanfile $nroffScanCT $manPageFH"
    (procedure "ProcessNroffFile" line 12)
    invoked from within
"ProcessNroffFile $manFile"
    (procedure "buildhelp" line 69)
    invoked from within
"buildhelp $helpDir $brief [list $tmpFile]"
    (file "/usr/src/RPM/BUILD/tcltk-8.3.3/tclx8.3/unix/tools/bldmanhelp" line 
148)
make[1]: *** [buildhelp] Error 255
make[1]: Leaving directory `/usr/src/RPM/BUILD/tcltk-8.3.3/tclx8.3/tcl/unix'
make: *** [TCLX_INSTALL] Error 2
make: Leaving directory `/usr/src/RPM/BUILD/tcltk-8.3.3/tclx8.3/unix'
Bad exit status from /var/tmp/rpm-tmp.9034 (%install)


Obviously something in my environment is not setup right? I have tcl and tk 
(etc.) versions 8.3.2-7mdk installed, and I believe that I have the latest 
groff packages:

[root@dell2pe SPECS]# rpm -qa|grep -i groff
groff-gxditview-1.17.1-2mdk
groff-1.17.1-2mdk
groff-perl-1.17.1-2mdk
groff-for-man-1.17.1-2mdk


I'm trying various workarounds, but no luck yet.

Anybody else had this problem? Have a solution?

-- 
Juhan Leemet
Logicognosis, Inc.

Reply via email to