Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!hao!noao!arizona!megaron!whm
From: whm@megaron.UUCP
Newsgroups: net.lang.c++
Subject: C++ installation on 4.3bsd
Message-ID: <952@megaron.UUCP>
Date: Fri, 21-Mar-86 15:54:42 EST
Article-I.D.: megaron.952
Posted: Fri Mar 21 15:54:42 1986
Date-Received: Tue, 25-Mar-86 03:05:58 EST
Distribution: net
Organization: Dept of CS, U of Arizona, Tucson
Lines: 30

I just installed C++ on our 4.3bsd VAXs and it didn't go too smoothly.
I looked through the accumulated news in this group and there seem to
be people that are running C++ on BSD systems and since there's been
no mention of any others having any trouble installing on BSD systems,
I was wondering if I managed to screw things up somehow.

The problems seemed to stem from differences in Sys5 and BSD make and sh.
For example, the instructions say to "make scratch" and issuing this
command executes the following:

    cd scratch;  CC=CC BSD=1 CCFLAGS="-O -DBSD"

Oops!  Looks like it got the variables set ok.  If it had only remembered
to do the make!  We've got the BRL Sys5 package and using its make got
around the problems with BSD make.  In the CC script itself, when run
with /bin/sh, you get a cryptic error about -a being an unrecognized
operator for "test".  Running with Sys5 sh fixes this.  Further along
in CC, the command "CC -o x x.c" eventually tries to do something like:

	cc -c -o x x..c
	mv x..o x.o

With BSD cc, the output file lands in "x", not x..o.  With Sys5 cc, the
output goes to x..o; -o is passed on to the loader (if called).

Also, there was no man page for CC other than the one included in the hardcopy
documentation.

Am I the only person who has encountered these problems with a BSD installation?
If not, does anybody have a CC that allows the BSD cc behavior?