Re: groff 1.17.2 fails to build under vax-dec-ultrix4.3

[Werner LEMBERG]

> > What do you mean with `fixincl'?  Can you provide a small autoconf
> > test to check the prototype of atexit (if in CC mode)?
> 
> This header problem should be fixed in gcc as it's going to be an
> ongoing issue with g++.  An include hack needs to be developed to
> implement the following change to the stdlib.h file installed in the
> gcc include directory.  This will fix the above problem.  I will try
> to do this.

OK, so I'll ignore this problem.

> While a small autoconf check could detect the problem, it seems kind
> of messy to work around.  Presumably, you want to include stdlib.h
> and use atexit?

? I don't know what you mean.  Please explain.

> > Hehe.  What else do people on Ultrix use?  Only mkstemp() is secure.
> 
> What is available in libc is mktemp, tmpnam and tmpfile.  I don't
> know enough about the security issues to make any recomendations.
> You might look at Jim Meyering's implementation of mkstemp.c in
> fileutils.  This is probably much better than what exists in ultrix
> 4.3.

tmpnam() should never be used, tmpfile() is OK but doesn't return the
name of the created temporary file.

mktemp() shouldn't be used either (since it only creates, similar to
tmpnam() a file name without immediately opening it).

Maybe I'll adapt Jim's mkstemp to groff.  Due to the endless problems
it might be the best solution.  Thanks for the pointer.

> Would have thought that a configure check for the declaration of
> mktemp would be the way to go.

Right, this is even better.


     Werner