From: "Juan Manuel Guerrero" <ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De>
Organization: Darmstadt University of Technology
To: djgpp AT delorie DOT com
Date: Thu, 2 Dec 1999 10:11:01 +0100
Subject: minor bug in groff-1.10
X-mailer: Pegasus Mail for Windows (v2.54DE)
Message-ID: <32B4E51F37@HRZ1.hrz.tu-darmstadt.de>
Reply-To: djgpp AT delorie DOT com

When I have tried to compile groff-1.10 from sources (gro110s.zip)
I always got the following error message:

make.exe[2]: Entering directory `d:/_/groff-1.10/libgroff'
gcc -I. -I. -I../include -I./../include -DHAVE_UNISTD_H=1  -DHAVE_DIRENT_H=1
  -DHAVE_LIMITS_H=1  -DHAVE_SYS_DIR_H=1  -DHAVE_STDLIB_H=1  -DUNISTD_H_DECLARES_GETOPT=1
  -DSTDLIB_H_DECLARES_PUTENV=1  -DSTDIO_H_DECLARES_POPEN=1  -DSTDIO_H_DECLARES_PCLOSE=1
  -DHAVE_CC_OSFCN_H=1  -DHAVE_CC_LIMITS_H=1  -DRETSIGTYPE=void  -DHAVE_STRUCT_EXCEPTION=1
  -DHAVE_RENAME=1  -DHAVE_MKSTEMP=1   -g -O  -c new.cc
In file included from ../include/posix.h:25,
                 from new.cc:24:
g:/lang/cxx/osfcn.h:9: sys/socket.h: No such file or directory (ENOENT)
make.exe[2]: *** [new.o] Error 1
make.exe[2]: Leaving directory `d:/_/groff-1.10/libgroff'
make.exe[1]: *** [libgroff] Error 2
make.exe[1]: Leaving directory `d:/_/groff-1.10'
make.exe: *** [all] Error 2

This minor problem can be solved by reconfiguring the sources
running the file: djgpp/config.bat.
The only reason why I mention this is because the README
file tells that the sources are already configured for DJGPP.
This seems not to be true.
After reconfiguration the define:
  -DHAVE_CC_OSFCN_H=1
is deleted.
After reconfiguring the sources compilation and installation
works as expected.

I tried then to create a postscript file. The ps output was
created an was O.K. but I got always the following error message:

g:\bin/grops.exe:<standard input>:4: cannot unlink `g:/tmp/gfXXXXXX': No such file
or directory (ENOENT)

On TMPDIR (= g:/tmp) a file called gfaaaaaa (this time) always remains undeleted.
Once again: the output is O.K. but grops.exe is not able to delete the
temporary file it creats. This is the minor bug i wanted to report.
I have not tested for dvi and other type of output.
May be the same bug appears in grodvi.exe and grolj4.exe too.
ASCII output works fine.

It should be noted that the binaries from gro110b.zip also
work fine.

Regards,
Guerrero, Juan Manuel