Patch for variable arguments bug in Tinyfugue (screen corruption) (Cont.)

Continued from Patch for variable arguments bug in Tinyfugue (screen corruption)

I was looking at Tinyfugue's source code in order to see what exactly is currently being used from the ncurses library.  I was curious about whether Tinyfugue was currently using any of the main ncurses code for display purposes, or if ncurses was just being used for the termcap information.  That's when I noticed that the ./configure output from the RHEL 3 machine was different from my Ubuntu machine.

RHEL 3:
checking for library containing tgetent... -lncurses

Ubuntu:
checking for library containing tgetent... no
configure: WARNING: Hardcoding terminal codes.

Quite simply, I didn't have the ncurses development libraries installed.  Not a huge deal since getting them from the apt repositories is pretty easy.

The surprise came when I ran a new configure on the original Tinyfugue source (without the va_list patch).  Once I ran Tinyfugue, there was no screen corruption.  I was pretty shocked.  I thought maybe I was running on an unclean directory.  So I started from scratch and after compiling, Tinyfugue was running with no screen corruption.  I went ahead and uninstalled the ncurses development library, cleaned and compiled Tinyfugue, and once again there was screen corruption.

My conclusion is that something with ncurses (either ncurses itself or with how Tinyfugue builds the code in the first place) that prevents the issue with the va_list I experienced.  I'm not going to look to0 much in to this because with my va_list patch, the issue is resolved in both ncurses and non-ncurses builds.