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

[Jeffrey A Law <law at cygnus dot com>]

  In message <19980826185508.A27094@dot.cygnus.com>you write:
  > On Wed, Aug 26, 1998 at 07:40:42PM -0600, Jeffrey A Law wrote:
  > >   > 	The branch is fine.  This issue arose after installation of
  > >   > the following patch, which is only in the mainline sources:
  > > Weird.  I thought we had installed that patch on the branch.  I guess
  > > not.
  > 
  > So did I, which is what threw me.
I just checked the repo, and it's definitely not on the branch, nor
was it ever on the branch.  I guess we "chickened out" installing it
for fear of breaking something (or we just forgot).


  > 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