Re: bad change to ginclude/va-alpha.h

["Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>]

 > From: Jeffrey A Law <law@hurl.cygnus.com>
 > 
 >   > I can in fact reproduce the problem
 >   > here.  I've a new version of va_list.h that seems to work (attached).
 >   > 
 >   > The question is, do we put it in ginclude/ and add it to EXTRA_INCLUDES
 >   > for osf, or put it under config/alpha/ and do the same, or do something
 >   > funky with fixincludes?
 > Ugh.  I'd lean towards putting it in ginclude and adding it to
 > EXTRA_HEADERS.  It wouldn't suprise me if OSF was the only vendor to
 > go this direction, so we might be able to reuse this on another port.
 > 
 > I'd try to avoid fixincludes if possible :-) :-)
 > jeff

	I don't think we can reuse this particular file on another port,
because it seems closely patterned after the system version of
/usr/include/va_list.h which leads me to suspect its tied to the OS. 

	That leads me to another question, on what particular versions
of OSF would we use it?  I.e., do we need it on 3.x?  Do we need it on all
4.x versions?  Would we use the same replacement va_list.h on all
versions?  Ugh.

	Anyway, I'm happy to test a final fix, assuming I can get it in
patch form.  :-)

		--Kaveh