Re: LYNX-DEV scrollok and lynx_force_repaint

[T.E.Dickey]

>       But one other remaining problem is that when building with
> slang on osf you get gobs of "redefinition of macro va_start"
> warnings.  They can be ignored because Lynx doesn't use va_start(),
> but many OSFers are displayed VMSers, and feel uncomfortable about
> using an image that had lots of warnings when it was being built.
> Is there any way to deal with that, short of editing system headers?
I encountered this on AIX, investigated & found it was due (on that
system) to an incorrectly ifdef'd partial definition for <stdarg.h>
which was embedded in <stdio.h> - a similar problem was reported for
Ultrix.  If this is the case for OSF/1, then editing system headers is
the only way to fix it.

-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;