Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!topaz!ll-xn!nike!ucbcad!ucbvax!decvax!bellcore!petrus!sabre!python!michael
From: michael@python.UUCP (M. Cain)
Newsgroups: net.lang.c++
Subject: looking for help porting C++
Message-ID: <194@python.UUCP>
Date: Thu, 17-Jul-86 08:36:10 EDT
Article-I.D.: python.194
Posted: Thu Jul 17 08:36:10 1986
Date-Received: Fri, 18-Jul-86 05:16:28 EDT
Distribution: net
Organization: Bell Communications Research
Lines: 28

I'm trying to port C++ to a Hewlett-Packard 550 running
HPUX.  I was able to make cfront from the ..c files in
the distribution.  However, cfront complains that "this
c does not support varargs" when compiling some parts of
the library and the C++ source for cfront.  HPUX *does*
support varargs -- but the 550 runs its stack "backwards"
from the way its done on a VAX.

Taking one of the guidelines to heart, I checked to see
if the HPUX header files were compatible with the headers
in the distribution.  Varargs.h certainly wasn't.  Since
I have limited access to a VAX, I built a working cfront
there, changed varargs.h to reflect the 550 way of doing
things, and compiled the .c files to produce new ..c files.
Took those back to the 550.  No difference.

Grepping the C++ source for cfront and the distributed
include files, I found that none of them reference varargs.h.
This seems to imply that the code hardwires assumptions about
the stack, rather than using the stuff in varargs.h.

Questions:  Has anyone else had this problem in doing a port?
Does anyone have any suggestions for fixing the problem?
Thanks in advance for any advice...

Mike Cain
Bell Communications Research
..!python!michael