jon@csvax.caltech.edu (Jonathan P. Leech) (03/13/86)
Help! We just got the updated version of C++ (Release 1.0) and I'm
having lots of trouble installing it. Release E went in with no
trouble on VAX/4.2 BSD but broke the Sun 1.0 C compiler. I'm trying to
install Release 1 on several Unix variants and they each have
different problems:
Amdahl UTS (System V)
The installation guide says to just 'make scratch'; however,
the order of members in a FILE is different for
/usr/include/stdio.h and the supplied stdio.h for C++. The
documentation claims this should only be true for non System Vs.
Is it sufficient to change the C++ header?
Sun 2.0 (BSD derived)
So far all the shell scripts break since they either do not
include #!/bin/sh or do not put it as the first line of the file.
After correcting this, C++ boostraps from the supplied C source,
but the shell script CC does not work (complains about 'test -a'
buried somewhere in the file).
I also need to install C++ on VAX/4.2 BSD and (later) HP/UX
(supposedly System V) for HP Series 300 workstations. Has ANYONE had
success installing the new C++ on a non-AT&T machine? If so, please
let me know what you had to do.
Thanks,
Jon Leech (jon@csvax.caltech.edu)
__@/jsdy@hadron.UUCP (Joseph S. D. Yao) (03/22/86)
In article <1762@brl-smoke.ARPA> jon@csvax.caltech.edu (Jonathan P. Leech) writes: > the order of members in a FILE is different for > /usr/include/stdio.h and the supplied stdio.h for C++. The > documentation claims this should only be true for non System Vs. > Is it sufficient to change the C++ header? I've never used C++; but nobody else has responded, and I figured I'd take on at least this. If and only if C++ source files always compile with their very own set of include files a n d libc.a, then you must leave the stdio.h file as it is. The FILE is only an in-core representation, and doesn't correspond to anything in the external environment. However, as I understand it, C++ is only a pre-processor, and relies on cc to do the rest of its work. In that case (and assuming you're not talking about just compiling c++ itself), you must use the FILE structure that is compiled into libc.a; i.e., the one in <stdio.h>. If you have to mix a C++ library (that uses FILE's) and your native C library ... you're out of luck. I suspect you may have known this; I post this just in case you didn't, and to prime the pump. You may get better response by re-posting to net.c++. -- Joe Yao hadron!jsdy@seismo.{CSS.GOV,ARPA,UUCP}
jsdy@hadron.UUCP (Joseph S. D. Yao) (03/22/86)
In article <326@hadron.UUCP> jsdy@hadron.UUCP (I) write: >net.c++. I meant net.lang.c++, of course. (*sigh*) -- Joe Yao hadron!jsdy@seismo.{CSS.GOV,ARPA,UUCP}