[comp.lang.c++] compiling NIHCL on a Sun SPARC

gerson@parc.xerox.com (Dan Gerson) (10/05/90)

When I try to compile NIHCL v3.0 on a SPARC architecture (4/330) under SunOS
4.0.3, NIHCL's use of __builtin_va_alist causes Sun's AT&T C++ 2.0 FCS to die
claiming that __builtin_va_alist is redefined and that there are parameters
after va_alist.

It seems to compile ok (although I haven't finished it yet) if I disable this
hack.  Does anyone know whether this stdarg hack is still necessary, or is it ok
to disable it?

Dan Gerson
Xerox Palo Alto Research Center
--

Dan Gerson					gerson@parc.xerox.com
Xerox Palo Alto Research Center			415-494-4745
3333 Coyote Hill Road
Palo Alto, CA 94304
USA

kgorlen@sparkler.dcrt.nih.gov (Keith Gorlen) (10/06/90)

In article <GERSON.90Oct4133614@dupin.parc.xerox.com>,
gerson@parc.xerox.com (Dan Gerson) writes:
|>When I try to compile NIHCL v3.0 on a SPARC architecture (4/330) under SunOS
|>4.0.3, NIHCL's use of __builtin_va_alist causes Sun's AT&T C++ 2.0 FCS to die
|>claiming that __builtin_va_alist is redefined and that there are parameters
|>after va_alist.
|>
|>It seems to compile ok (although I haven't finished it yet) if I disable this
|>hack.  Does anyone know whether this stdarg hack is still necessary,
or is it ok
|>to disable it?
|>
|>Dan Gerson
|>Xerox Palo Alto Research Center
|>--
|>
|>Dan Gerson					gerson@parc.xerox.com
|>Xerox Palo Alto Research Center			415-494-4745
|>3333 Coyote Hill Road
|>Palo Alto, CA 94304
|>USA
 
It's OK to disable it.  I put it in for AT&T C++ R2.0/R2.1.
                 
	Keith Gorlen			phone: (301) 496-1111
	Building 12A, Room 2033		uucp: uunet!nih-csl!kgorlen
	National Institutes of Health	Internet: kgorlen@alw.nih.gov
	Bethesda, MD 20892