Conference smurf::buildhelp

2625.0. "shared sandbox build" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Wed Oct 23 1996 21:08

Date Of Receipt: 	23-OCT-1996 16:18:50.86
From: 	HUNCH::"corbin@kit.zk3.dec.com"
To: 	buildhelp@zk3.dec.com
CC: 	corbin@kit.zk3.dec.com
Subj: 	shared sandbox build

I am having a problem building subdirectories in a shared sandbox.
I modified some Makefiles to change the SUBDIR list and the builds
worked fine in a private sandbox backed by the shared sandbox.  After
the Makefiles were checked into the shared sandobx the private sandbox
continued to operate properly.

But doing the build in the sahred sandbox does not pick up the Makefile
changes, it appears to pick up the Makefile from the backing tree.

More specifically:

    In private sandbox:

	1. Changed usr/ccs/lib/Makefile to use liblsm instead of libvxvm.

	2. Build usr/ccs/lib - builds subdir liblsm, not libxvm.

	3. Checkin and Bsubmit to shared sandbox (lsmproj).

    In shared sandbox:

	Usr/lib/ccs/Makefile is now a local copy, not a link.  The
	Makefile is exactly what was checked in

	4. Build -p show that the environment variables are using
	   libvxvm, not liblsm.  Libvxvm is what gets built.

I am assuming that the Makefile is being taken from the backing tree
(ptos.bl12) since that is the only Makefile with references to libvxvm
after the checkin.

- steve corbin