🚀 go-pugleaf

While installing the latest distribution of GNU Finger 1.36, I have
encountered two problems so far:

On a SUN 670 MP running SUN OS release 4.1.2, the header files appear
to be non-ANSI as distributed: in particular, the declarations of
abort and exit are wrong (the return codes are declared as 'int').
The configure script does not notice this and attempts to use them.
Since I have gcc installed, the configure script attempted to use it;
and gcc complained about this deficiency.  (I am curious about this
feature of gcc: I wasn't aware that any functions were built in and
could not be overridden.  Is there a way to turn this off, or at least
make it compile the file anyway (ignoring the incorrect declaration)?)
(As a workaround I used the standard C compiler, since I didn't know
how to turn off the feature of gcc, didn't notice the DSTDC_HEADERS
option, and didn't want to modify the header files.  Sorry.)

On an IRIS Indigo (System V release 4.0.2), the standard C compiler
seems to be remarkably pedantic.  It gives the following message
(while working in the lib directory):

accom: Error: packet.c, line 521: static function declaration in inner block is illegal (ANSI C 3.5.1)
         static int read_component ();
       ------------------------------^

It gives the same error again, in in.fingerd.c.  Also, in os.c it
whines that 'text following '#endif' violates ANSI standard'.

(I lied, here's another problem.)  On the IRIS, alloca is defined ONLY
in the header file.  Thus, when lib/bitmap.c, lib/packet.c, and
src/finger.c try to use alloca without declaring it, it doesn't
working.  (From the top of getopt.c, it seems likely they'll have more
trouble under AIX as well.)  (Actually, this seems like it's a problem
in getopt.c as well.  I'll send a separate bug report on that.)

And one more comment--the message when finger can't find the port to
connect to is singularly unhelpful.  Is there any way to make it
better?