Conference smurf::buildhelp

Date Of Receipt: 	 9-MAR-1994 11:35:41.69
From: 	WASTED::eagle "David Eagle USG"
To: 	buildhelp@wasted:zko.dec
CC: 	
Subj: 	can't build

I am having serious difficulties creating a new sandbox.
I haven't been able to build in a week.  In general,
the build fails to find include files, but which include
files it fails to find changes depending on the exact
sequence of steps I take to create the sandbox, and
which machine I am on when I run the build.  Also, I
do  not always get a failure to find include files.
Sometimes I get a failure to find object files at the\

link step.  I have tried all the tricks I know and 
definitely need some handholding at this point.

Date Of Receipt: 	 9-MAR-1994 11:43:00.64
From: 	FLAMBE::jmf "Joshua M. Friedman ULTRIX SDE"
To: 	eagle@DEC:.zko.flambe
CC: 	buildhelp@DEC:.zko.flambe
Subj: 	Re:  can't build

Dave, my only question is - are you doing a full kernel build, that is,
do you start with an empty obj directory?  If you're trying to second-
guess dependencies and haven't built from scratch, I'd try that.

-josh
	From eagle  Wed Mar  9 11:35:19 1994
	Delivery-Date: Wed, 09 Mar 94 11:35:28 -0500
	Return-Path: eagle
	Received: from wasted.zk3.dec.com by flambe.zk3.dec.com; (5.65/1.1.8.2/04Mar94-1219PM)
		id AA20651; Wed, 9 Mar 1994 11:35:19 -0500
	Received: by wasted.zk3.dec.com; id AA13618; Wed, 9 Mar 1994 11:28:19 -0500
	Date: Wed, 9 Mar 1994 11:28:19 -0500
	From: David Eagle USG <eagle>
	Message-Id: <[email protected]>
	Subject: can't build
	Apparently-To: buildhelp
	
	I am having serious difficulties creating a new sandbox.
	I haven't been able to build in a week.  In general,
	the build fails to find include files, but which include
	files it fails to find changes depending on the exact
	sequence of steps I take to create the sandbox, and
	which machine I am on when I run the build.  Also, I
	do  not always get a failure to find include files.
	Sometimes I get a failure to find object files at the\
	
	link step.  I have tried all the tricks I know and 
	definitely need some handholding at this point.
	
!p

Date Of Receipt: 	 7-JUN-1996 15:34:02.79
From: 	20162::maggie "Maggie Peterson USG  07-Jun-1996 1508"
To: 	odehelp@DEC:.zko.wasted
CC: 	
Subj: 	can't build

hi,

i'm trying to build from sandbox/steelos/src/kernel
and i'm getting an error "../obj does not exist"

thanks,
maggie



shadow /home/maggie > kinit Maggie_Peterson
Kerberos Initialization for "Maggie_Peterson"
Password: 
shadow /home/maggie > su
Password:
# odemount steelos.nightly steelos
    secret on /tmp_mnt/share/secret/build/submits.dsk3: Device busy
    cia on /tmp_mnt/share/cia/build/ptos.dsk1: Device busy
# odemount steelos.nightly steelos
# exti
exti: not found
# exit
shadow /home/maggie > workon -sb steelos
cd'ing to sandbox source directory: /home/sb/steelos/src.
starting new shell: /usr/local/bin/tcsh.
shadow /home/sb/steelos/src > cd kernel
shadow /home/sb/steelos/src/kernel > build BINARY_ MAKE_ARGS=vfs_subr.o
relative path: ./kernel.
string passed to 
/usr/sde/osf1/build/steelos.nightly/tools/alpha_OSF1/alpha/hostbin/make:
   make -cF MAKE_ARGS=vfs_subr.o BINARY_ 
Make: No such directory: ../obj.  Stop.
shadow /home/sb/steelos/src/kernel > 

Date Of Receipt: 	 7-JUN-1996 15:40:49.01
From: 	FLUME::"[email protected]" "Susan Schueller USG  07-Jun-1996 1519"
To: 	[email protected]
CC: 	[email protected], [email protected]
Subj: 	Re: can't build

Hi Maggie,
 I'm taking a look at this right now for you.

Sue

> 
> hi,
> 
> i'm trying to build from sandbox/steelos/src/kernel
> and i'm getting an error "../obj does not exist"
> 
> thanks,
> maggie
> 
> 
> 
> shadow /home/maggie > kinit Maggie_Peterson
> Kerberos Initialization for "Maggie_Peterson"
> Password: 
> shadow /home/maggie > su
> Password:
> # odemount steelos.nightly steelos
>     secret on /tmp_mnt/share/secret/build/submits.dsk3: Device busy
>     cia on /tmp_mnt/share/cia/build/ptos.dsk1: Device busy
> # odemount steelos.nightly steelos
> # exti
> exti: not found
> # exit
> shadow /home/maggie > workon -sb steelos
> cd'ing to sandbox source directory: /home/sb/steelos/src.
> starting new shell: /usr/local/bin/tcsh.
> shadow /home/sb/steelos/src > cd kernel
> shadow /home/sb/steelos/src/kernel > build BINARY_ MAKE_ARGS=vfs_subr.o
> relative path: ./kernel.src/kernel > build BINARY_ MAKE_ARGS=
> string passed to kernel.src/kernel > build BINARY_ MAKE_ARGS=
> /usr/sde/osf1/build/steelos.nightly/tools/alpha_OSF1/alpha/hostbin/make:
>    make -cF MAKE_ARGS=vfs_subr.o BINARY_ 
> Make: No such directory: ../obj.  Stop.
> shadow /home/sb/steelos/src/kernel > 

-- 
------------------------------------------------------------
Susan Schueller              Digital Equipment Corporation
USG Release Engineering      MS ZKO3-3/W20
(603) 881-6348               110 Spit Brook Road
[email protected]         Nashua, NH 03062-2698
------------------------------------------------------------

Date Of Receipt: 	 7-JUN-1996 16:12:46.45
From: 	FLUME::"[email protected]" "07-Jun-1996 1612"
To: 	[email protected]
CC: 	[email protected]
Subj: 	Re: can't build

There is no obj tree for the submit tree, nor is there usually exports either. 
The submit trees are basically source only and not really designed to build 
against. Try using nightly instead.

		-Grant
| 
| hi,
| 
| i'm trying to build from sandbox/steelos/src/kernel
| and i'm getting an error "../obj does not exist"
| 
| thanks,
| maggie
| 
| 
| 
| shadow /home/maggie > kinit Maggie_Peterson
| Kerberos Initialization for "Maggie_Peterson"
| Password: 
| shadow /home/maggie > su
| Password:
| # odemount steelos.nightly steelos
|     secret on /tmp_mnt/share/secret/build/submits.dsk3: Device busy
|     cia on /tmp_mnt/share/cia/build/ptos.dsk1: Device busy
| # odemount steelos.nightly steelos
| # exti
| exti: not found
| # exit
| shadow /home/maggie > workon -sb steelos
| cd'ing to sandbox source directory: /home/sb/steelos/src.
| starting new shell: /usr/local/bin/tcsh.
| shadow /home/sb/steelos/src > cd kernel
| shadow /home/sb/steelos/src/kernel > build BINARY_ MAKE_ARGS=vfs_subr.o
| relative path: ./kernel.
| string passed to 
| /usr/sde/osf1/build/steelos.nightly/tools/alpha_OSF1/alpha/hostbin/make:
|    make -cF MAKE_ARGS=vfs_subr.o BINARY_ 
| Make: No such directory: ../obj.  Stop.
| shadow /home/sb/steelos/src/kernel > 

Date Of Receipt: 	 7-JUN-1996 16:16:01.32
From: 	FLUME::"[email protected]" "07-Jun-1996 1615"
To: 	[email protected]
CC: 	[email protected]
Subj: 	Re: can't build

Sorry, didn;t read to the bottom. Guess you already tried that.
Can't tell from the mail whether it's complaining about obj in your sb of the 
backingtree. Did you check the permissions/existance of obj in your sandbox?

		-Grant
| 
| hi,
| 
| i'm trying to build from sandbox/steelos/src/kernel
| and i'm getting an error "../obj does not exist"
| 
| thanks,
| maggie
| 
| 
| 
| shadow /home/maggie > kinit Maggie_Peterson
| Kerberos Initialization for "Maggie_Peterson"
| Password: 
| shadow /home/maggie > su
| Password:
| # odemount steelos.nightly steelos
|     secret on /tmp_mnt/share/secret/build/submits.dsk3: Device busy
|     cia on /tmp_mnt/share/cia/build/ptos.dsk1: Device busy
| # odemount steelos.nightly steelos
| # exti
| exti: not found
| # exit
| shadow /home/maggie > workon -sb steelos
| cd'ing to sandbox source directory: /home/sb/steelos/src.
| starting new shell: /usr/local/bin/tcsh.
| shadow /home/sb/steelos/src > cd kernel
| shadow /home/sb/steelos/src/kernel > build BINARY_ MAKE_ARGS=vfs_subr.o
| relative path: ./kernel.
| string passed to 
| /usr/sde/osf1/build/steelos.nightly/tools/alpha_OSF1/alpha/hostbin/make:
|    make -cF MAKE_ARGS=vfs_subr.o BINARY_ 
| Make: No such directory: ../obj.  Stop.
| shadow /home/sb/steelos/src/kernel > 

Date Of Receipt: 	 7-JUN-1996 16:18:55.62
From: 	FLUME::"[email protected]" "John Flanagan USG Test Johnf Tools Group  07-Jun-1996 1618"
To: 	"Grant Van Dyck" <[email protected]>
CC: 	[email protected], [email protected]
Subj: 	Re: can't build

Maggie's problem looked to me to be the classic "I deleted Makeconf from src"
problem.  Make has absolutely no idea where it is, and it is assuming the 
current working directory is the top of the tree [since Makeconf presumably
isn't there].
-- 


 ______________________________________________________________________

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

Date Of Receipt: 	 4-SEP-1996 08:16:57.42
From: 	WASTED::maggie "Maggie Peterson USG  04-Sep-1996 0815"
To: 	odehelp@DEC:.zko.wasted
CC: 	
Subj: 	can't build

hi,

do you know what's going on?  i have been building ok this morning, now i am 
getting errors because:

shadow /home/sb/steelnightly/src/kernel> ls /share/remington/build/steelos.dsk8 
/share/remington/build/steelos.dsk8 not found


thanks,
maggie

Date Of Receipt: 	14-OCT-1996 09:52:09.99
From: 	WASTED::maggie "Maggie Peterson USG  14-Oct-1996 0949"
To: 	odehelp@DEC:.zko.wasted
CC: 	
Subj: 	can't build

hi,

i made a new sandbox backed against steelos.nightly
did a "bco -u" of a file in src/kernel/vfs
but can't build:

shadow /home/sb/realnewsteel/src/kernel > build BINARY_ MAKE_ARGS=vfs_flock.o
relative path: ./kernel.
string passed to 
/usr/sde/osf1/build/steelos.nightly/tools/alpha_OSF1/alpha/hostbin/make:
   make -cF MAKE_ARGS=vfs_flock.o BINARY_ 
cd ../../obj/alpha/kernel
cd BINARY && make -cF vfs_flock.o 
KCC=/usr/sde/osf1/build/steelos.nightly/tools/alpha_OSF1/alpha/acc/cc  
LD=/usr/sde/osf1/build/steelos.nightly/tools/alpha_OSF1/alpha/acc/ld  CPP=cpp  
AWK=awk  AR=/usr/sde/osf1/build/steelos.nightly/tools/alpha_OSF1/alpha/acc/ar  
RANLIB='/usr/sde/osf1/build/steelos.nightly/tools/alpha_OSF1/alpha/acc/ar ts'  
SHELL=sh  SED=sed  SORT=sort  ECHO=echo  KSH=ksh  EGREP=egrep  GREP=grep  
LINT=lint CONFIG=BINARY 
/usr/sde/osf1/build/steelos.nightly/tools/alpha_OSF1/alpha/acc/cc  -c -O2   
-DLANGUAGE_C -g1  -I -I. -I.. -I../include -DIDENT=BINARY -DMACH -DOSF 
-DCOMPAT_43 -DESS -DESS_STUB -DKERNEL -D_KERNEL -D_BSD -DBINARY -MD -w2 
-compress  -no_excpt -Wg,-unroll,1 -Wb,-static -Wco,-nofloat -Umips -UMIPS 
-U__intel__ -D__alpha -D__digitaal__ -D__arch64__ -g3 
../../../../src/kernel/vfs/vfs_flock.c
cc: Fatal: A memory access violation (bus error or segmentation fault)
has occurred.  Please submit a problem report.
objZ: can not read file header - vfs_flock.o
*** Exit 1
Stop.
*** Exit 1
Stop.

Date Of Receipt: 	14-OCT-1996 12:29:17.03
From: 	FLUME::"[email protected]"
To: 	[email protected] (maggie)
CC: 	[email protected], [email protected] (Andrew Duane USG/PE)
Subj: 	Re: can't build

Did you happen to see Andrew's mail last Fri to osf_developers about major
changes to the Steel and PTC kernel build?  It will basically require you to
start with a  clena sand box or else follow the instructon he provided. There
are major changes to the Kernel makefiles and template.mk files. Your build
should go much faster now, but will require you to start with a clean slate.

> 
> hi,
> 
> i made a new sandbox backed against steelos.nightly
> did a "bco -u" of a file in src/kernel/vfs
> but can't build:
> 
> shadow /home/sb/realnewsteel/src/kernel > build BINARY_ MAKE_ARGS=vfs_flock.o
> relative path: ./kernel.
> string passed to 
> /usr/sde/osf1/build/steelos.nightly/tools/alpha_OSF1/alpha/hostbin/make:
>    make -cF MAKE_ARGS=vfs_flock.o BINARY_ 
> cd ../../obj/alpha/kernel
> cd BINARY && make -cF vfs_flock.o 
> KCC=/usr/sde/osf1/build/steelos.nightly/tools/alpha_OSF1/alpha/acc/cc  
> LD=/usr/sde/osf1/build/steelos.nightly/tools/alpha_OSF1/alpha/acc/ld  CPP=cpp  
> AWK=awk  AR=/usr/sde/osf1/build/steelos.nightly/tools/alpha_OSF1/alpha/acc/ar  
> RANLIB='/usr/sde/osf1/build/steelos.nightly/tools/alpha_OSF1/alpha/acc/ar ts'  
> SHELL=sh  SED=sed  SORT=sort  ECHO=echo  KSH=ksh  EGREP=egrep  GREP=grep  
> LINT=lint CONFIG=BINARY 
> /usr/sde/osf1/build/steelos.nightly/tools/alpha_OSF1/alpha/acc/cc  -c -O2   
> -DLANGUAGE_C -g1  -I -I. -I.. -I../include -DIDENT=BINARY -DMACH -DOSF 
> -DCOMPAT_43 -DESS -DESS_STUB -DKERNEL -D_KERNEL -D_BSD -DBINARY -MD -w2 
> -compress  -no_excpt -Wg,-unroll,1 -Wb,-static -Wco,-nofloat -Umips -UMIPS 
> -U__intel__ -D__alpha -D__digitaal__ -D__arch64__ -g3 
> ../../../../src/kernel/vfs/vfs_flock.c
> cc: Fatal: A memory access violation (bus error or segmentation fault)
> has occurred.  Please submit a problem report.
> objZ: can not read file header - vfs_flock.o
> *** Exit 1
> Stop.
> *** Exit 1
> Stop.
> 
> 


-- 

				-Grant

Date Of Receipt: 	14-OCT-1996 12:55:04.43
From: 	FLUME::"[email protected]" "Shashi Mangalat USG  14-Oct-1996 1252"
To: 	[email protected], [email protected]
CC: 	[email protected]    (maggie), [email protected],
	[email protected] (Andrew    Duane USG/PE)
Subj: 	Re: can't build

I ran into the same problem this morning.  It looks like cc has
problems dealing with a .d file that is a non-writable symlink.  I have
my obj tree linked to the backing tree's obj.  Once I removed the link
the compilation proceeded successfully.

--shashi