Conference smurf::buildhelp

Date Of Receipt: 	29-NOV-1994 17:59:46.96
From: 	ALPHA::jmf "Joshua M. Friedman OSF/UNIX SDE"
To: 	[email protected], [email protected]
CC: 	[email protected], [email protected]
Subj: 	Re:  where did all these header files go in /usr/sde/disks/odie_ra131c/ptos.nightly ?

Sunil, looking in the pool, the only thing in directory kernel/include/sys
is a makefile, which uses VPATH to point to where the sources are:

VPATH                   = ${MAKETOP}/kernel/sys:${MAKETOP}/kernel/io/dec/ws


You'll find the "missing" files in kernel/sys.  They were always here;
they were never in kernel/include/sys on the SRC side, only on the OBJ side.

-josh


	From [email protected]  Tue Nov 29 16:33:50 1994
	Delivery-Date: Tue, 29 Nov 94 16:34:17 -0500
	Return-Path: [email protected]
	Received: from ds9.unx.dec.com by flambe.zk3.dec.com; (5.65/1.1.8.2/30Mar94-0502PM)
		id AA24638; Tue, 29 Nov 1994 16:33:50 -0500
	Received: by ds9.unx.dec.com; id AA30301; Tue, 29 Nov 1994 16:33:48 -0500
	Message-Id: <[email protected]>
	To: [email protected]
	Cc: [email protected], [email protected], [email protected]
	Subject: where did all these header files go in /usr/sde/disks/odie_ra131c/ptos.nightly ? 
	Date: Tue, 29 Nov 94 16:33:47 -0500
	From: [email protected]
	X-Mts: smtp
	
	
	
	Dear odehelp,
	
	this is bewildering: where did all these header files go in 
	/usr/sde/disks/odie_ra131c/ptos.nightly   ?
	
	
	thanks,
	Sunil.
	
	
	===========================
	
	1308 /spec1170/sandbox/sb/sunil>currentsb -back
	/usr/sde/disks/odie_ra131c/ptos.nightly
	
	 1346 /spec1170/sandbox/sb/src/kernel/include/sys>echo $WORKON
	1
	
	 1347 /spec1170/sandbox/sb/src/kernel/include/sys>bsh ls -l ioctl.h procset.h siginfo.h signal.h types.h
	
	cd /usr/sde/osf1/build/ptos.nightly/src/kernel/include/sys
	ioctl.h not found
	procset.h not found
	siginfo.h not found
	signal.h not found
	types.h not found
	 1348 /spec1170/sandbox/sb/src/kernel/include/sys>incl4
	 1349 /spec1170/sandbox/sb/src/usr/include/sys>bsh ls -l ioctl.h procset.h siginfo.h signal.h types.h
	
	cd /usr/sde/osf1/build/ptos.nightly/src/usr/include/sys
	ioctl.h not found
	procset.h not found
	siginfo.h not found
	signal.h not found
	types.h not found
	 1350 /spec1170/sandbox/sb/src/usr/include/sys>incl
	 1351 /spec1170/sandbox/sb/src/usr/include>bsh ls -l ioctl.h procset.h siginfo.h signal.h types.h
	
	cd /usr/sde/osf1/build/ptos.nightly/src/usr/include
	ioctl.h not found
	procset.h not found
	siginfo.h not found
	signal.h not found
	types.h not found
	 1352 /spec1170/sandbox/sb/src/usr/include>incl3
	 1353 /spec1170/sandbox/sb/src/usr/include/alpha>bsh ls -l ioctl.h procset.h siginfo.h signal.h types.h
	
	cd /usr/sde/osf1/build/ptos.nightly/src/usr/include/alpha
	ioctl.h not found
	procset.h not found
	siginfo.h not found
	signal.h not found
	types.h not found
	===========================
	
	

Date Of Receipt: 	 6-APR-1995 15:53:48.95
From: 	SMURF::WASTED::"[email protected]" "06-Apr-1995 1252"
To: 	John Flanagan - UNIX Systems Group <[email protected]>
CC: 	[email protected], [email protected]
Subj: 	Re: ptos.nightly

Can you explain why this is in the shared file in the
ptos.nightly tree.

local.sharedsandbox:source_testdir /usr/sde/osf1/build/ptos.nightly1/src
shared:replace sandbox_base /usr/sde/osf1/build/ptos.nightly1

the path to make is

	/usr/sde/osf1/build/ptos.nightly1/tools

	Either our sup is not right or the pool we are supping is not right.
	Can you check this on your end.

Thanks in advance,
Craig Jordan

Date Of Receipt: 	 6-APR-1995 16:05:17.49
From: 	SMURF::FLUME::johnf "John Flanagan USG Test Johnf Tools Group  06-Apr-1995 1604"
To: 	[email protected]
CC: 	John Flanagan - UNIX Systems Group    <[email protected]>,
	[email protected]
Subj: 	Re: ptos.nightly

Craig,

The process that handles the toggling of our nightly trees had a failure and
left the specific tree name in those two rc_files.  The correct entries should
look as follows:

local.sharedsandbox:source_testdir /usr/sde/osf1/build/ptos.nightly/src
shared:replace sandbox_base /usr/sde/osf1/build/ptos.nightly


This will fix the error in finding the right make.  We've fixed this locally,
so you can either resup the tree, or change those two rc_files on your end.

Thanks for bringing this to our attention.

John


 ______________________________________________________________________

 John Flanagan	 		enet:    [email protected]	
 MS: ZKO3-3/W20			decnet:  flambe::johnf
 USG Release Engineering		 (603) 881-1719
 110 Spitbrook Road 			 (DTN) 381-1719
 Nashua, NH  
 ______________________________________________________________________

Date Of Receipt: 	27-APR-1995 08:54:13.81
From: 	SMURF::FLUME::daniele "Mike Daniele  27-Apr-1995 0850"
To: 	odeadmin@DEC:.zko.flume
CC: 	
Subj: 	ptos.nightly

Is it really built each night?  I'm just wondering
when in general one should expect to see their submits
in the nightly tree.  And specifically, things submitted
yesterday :-)

Thanks,
Mike

Date Of Receipt: 	27-APR-1995 09:06:24.12
From: 	SMURF::FLUME::johnf "John Flanagan USG Test Johnf Tools Group  27-Apr-1995 0858"
To: 	Mike Daniele <daniele@DEC:.zko.flume>
CC: 	odeadmin@DEC:.zko.flume, johnf@DEC:.zko.flume, mwarren@DEC:.zko.flume
Subj: 	Re: ptos.nightly

The ptos nightly build goes off every night, however, ptos.nightly only
gets updated when the build is good.  Last night's build was bad.  In the case
of a bad nightly build, the contents of the bad nightly are put in 
ptos.nightly.standby.  So, if you look in the standby tree, you'll see your
submits.

We may "toggle" nightly later this morning, as the build failure was localized
to two rarely used kernels.

John


 ______________________________________________________________________

 John Flanagan	 		enet:    [email protected]	
 MS: ZKO3-3/W20			decnet:  flambe::johnf
 USG Release Engineering		 (603) 881-1719
 110 Spitbrook Road 			 (DTN) 381-1719
 Nashua, NH  
 ______________________________________________________________________