Date: Thu, 2 Dec 1999 16:20:48 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Juan Manuel Guerrero <ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De>
cc: djgpp AT delorie DOT com
Subject: Re: minor bug in groff-1.10
In-Reply-To: <32B4E51F37@HRZ1.hrz.tu-darmstadt.de>
Message-ID: <Pine.SUN.3.91.991202161206.16478B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 2 Dec 1999, Juan Manuel Guerrero wrote:

> This minor problem can be solved by reconfiguring the sources
> running the file: djgpp/config.bat.

This is the right solution for this problem.

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

Groff was built with DJGPP v2.01, and was configured for that
version.  If you build it with another version of DJGPP, it needs
to be reconfigured.

In general, it is always better to run the configuration procedure.  The 
sources come configured for those who don't have Bash and the auxiliary 
tools installed, and therefore cannot run the configure scripts.

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

This is a known bug with the PostScript driver.  If you can spot where 
the bug is, please post the info here (and suggest a patch, if you can).  
If not, somebody will get to that in due time.  As you noticed, the bug 
is harmless.

> May be the same bug appears in grodvi.exe and grolj4.exe too.

The DVI and LJ4 drivers are free from this bug.