Conference smurf::buildhelp

1514.0. "URGENT ptos.nightly build problem!" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Tue Jun 06 1995 07:11

Date Of Receipt: 	 6-JUN-1995 05:12:15.51
From: 	SMURF::FLUME::"[email protected]" "06-Jun-1995 0510"
To: 	[email protected]
CC: 	
Subj: 	URGENT ptos.nightly build problem!

Hi buildhelp,

We have a very URGENT problem here at UNX. The problem is simply neither
I (nor one my co-workers) can build against ptos.nightly. The latest
error is:
  /usr/sde/osf1/build/ptos.nightly/src/kernel/nfs/nfs3_vnodeops.c
cc: Warning: /usr/sde/osf1/build/ptos.nightly/src/kernel/nfs/nfs3_vnodeops.c, li
ne 372: The redefinition of the macro "SEC_REMOTE" conflicts with a current defi
nition because the replacement lists differ.  The redefinition is now in effect.
#define SEC_REMOTE      0
------------------------^
cc: Error: /usr/sde/osf1/build/ptos.nightly/src/kernel/nfs/nfs3_vnodeops.c, line
 633: In this statement, "r_rwlock" is not a member of "rp".
        lock_read(&rp->r_rwlock);
-------------------^
cc: Error: /usr/sde/osf1/build/ptos.nightly/src/kernel/nfs/nfs3_vnodeops.c, line
 690: In this statement, "r_rwlock" is not a member of "rp".
        lock_done(&rp->r_rwlock);
-------------------^
cc: Error: /usr/sde/osf1/build/ptos.nightly/src/kernel/nfs/nfs3_vnodeops.c, line
 1822: In this statement, "r_rwlock" is not a member of "((struct rnode ...)((vp
)->v_data))".
        lock_read(&vtor(vp)->r_rwlock);
-------------------^
cc: Error: /usr/sde/osf1/build/ptos.nightly/src/kernel/nfs/nfs3_vnodeops.c, line
 1934: In this statement, "r_rwlock" is not a member of "((struct rnode ...)((vp
)->v_data))".
        lock_done(&vtor(vp)->r_rwlock);
-------------------^
cc: Error: /usr/sde/osf1/build/ptos.nightly/src/kernel/nfs/nfs3_vnodeops.c, line
 2118: In this statement, "r_rwlock" is not a member of "((struct rnode ...)((dv
p)->v_data))".
        lock_write(&vtor(dvp)->r_rwlock);
--------------------^
cc: Error: /usr/sde/osf1/build/ptos.nightly/src/kernel/nfs/nfs3_vnodeops.c, line
 2160: In this statement, "r_rwlock" is not a member of "((struct rnode ...)((dv
p)->v_data))".
        lock_done(&vtor(dvp)->r_rwlock);
-------------------^
cc: Error: /usr/sde/osf1/build/ptos.nightly/src/kernel/nfs/nfs3_vnodeops.c, line
 2245: In this statement, "r_rwlock" is not a member of "((struct rnode ...)((nn
dp->ni_dvp)->v_data))".
        lock_write(&vtor(nndp->ni_dvp)->r_rwlock);
--------------------^
cc: Error: /usr/sde/osf1/build/ptos.nightly/src/kernel/nfs/nfs3_vnodeops.c, line
 2248: In this statement, "r_rwlock" is not a member of "((struct rnode ...)((on
dp->ni_dvp)->v_data))".
                lock_write(&vtor(ondp->ni_dvp)->r_rwlock);
----------------------------^
cc: Error: /usr/sde/osf1/build/ptos.nightly/src/kernel/nfs/nfs3_vnodeops.c, line
 2286: In this statement, "r_rwlock" is not a member of "((struct rnode ...)((on
dp->ni_dvp)->v_data))".
                lock_done(&vtor(ondp->ni_dvp)->r_rwlock);
---------------------------^
cc: Error: /usr/sde/osf1/build/ptos.nightly/src/kernel/nfs/nfs3_vnodeops.c, line
 2287: In this statement, "r_rwlock" is not a member of "((struct rnode ...)((nn
dp->ni_dvp)->v_data))".
        lock_done(&vtor(nndp->ni_dvp)->r_rwlock);
-------------------^
cc: Error: /usr/sde/osf1/build/ptos.nightly/src/kernel/nfs/nfs3_vnodeops.c, line
 2487: In this statement, "r_rwlock" is not a member of "((struct rnode ...)((nd
p->ni_dvp)->v_data))".
        lock_write(&vtor(ndp->ni_dvp)->r_rwlock);
--------------------^
cc: Error: /usr/sde/osf1/build/ptos.nightly/src/kernel/nfs/nfs3_vnodeops.c, line
 2511: In this statement, "r_rwlock" is not a member of "((struct rnode ...)((nd
p->ni_dvp)->v_data))".
        lock_done(&vtor(ndp->ni_dvp)->r_rwlock);
-------------------^
*** Exit 1
Stop.
*** Exit 1
Stop.
$ 

We have have tried many times (including blowing away entirely our sandbox,
and starting afresh).


Our team lead has us scheduled to "drop" in the upcoming PRE BL7 build.

We can not "build", and hence cannot "test".

We have both built and tested against "BL5". However, there are hundreads
of lines of code that is different in the code (that we tested) and the
proposed "drop". Yet, we can not even compile - more less test this new
code!


We need your urgent attention on this matter.


Our team lead has suggested that we ask for the pre BL7 close date be moved
up, since we have tried for about 7 weeks now, and yet can not get a
(nightly) "kernel" that has all of our stuff in it (to test with).


Floyd,