Conference smurf::buildhelp

1395.0. "cluster pool s loader core dumps" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Tue Apr 18 1995 17:19

Date Of Receipt: 	11-APR-1995 12:45:23.83
From: 	SMURF::WASTED::grava "Bill Grava USG  11-Apr-1995 1244"
To: 	odehelp@DEC:.zko.wasted
CC: 	zap@DEC:.zko.wasted, rafiey@DEC:.zko.wasted, bstevens@DEC:.zko.wasted,
	grava@DEC:.zko.wasted
Subj: 	cluster pool's loader core dumps

I started a build in a sandbox with a completely clean obj tree this
morning after the notification that the clustwav3os.nightly build
had completed successfully. Things apparently went fairly well, =

until I got to the last step. This is what happens:
<sablelab1:/big1/sandbox/newclust/src/kernel> build SABLE_vmunix
relative path: ./kernel.
cd ../../obj/alpha/kernel
cd SABLE && make -cF  KCC=3D/usr/sde/osf1/build/clustwav3os.nightly/tools=
/alpha_
OSF1/alpha/acc/cc  LD=3D/usr/sde/osf1/build/clustwav3os.nightly/tools/alp=
ha_OSF1
/alpha/acc/ld  CPP=3Dcpp  AWK=3Dawk  AR=3D/usr/sde/osf1/build/clustwav3os=
=2Enightly/to
ols/alpha_OSF1/alpha/acc/ar  RANLIB=3D'/usr/sde/osf1/build/clustwav3os.ni=
ghtly/t
ools/alpha_OSF1/alpha/acc/ar ts'  SHELL=3Dsh  SED=3Dsed  SORT=3Dsort  ECH=
O=3Decho  =

KSH=3Dksh  EGREP=3Degrep  GREP=3Dgrep  LINT=3Dlint CONFIG=3DSABLE vmunix
sh ../conf/newvers.sh  ../conf/copyright  `cat ../conf/version.type  =

=2E./conf/version.major  ../conf/version.minor  ../conf/version.variant  =

=2E./conf/version.build  ../conf/version.patch`  "`cat ../conf/version.ba=
nner`"
/usr/sde/osf1/build/clustwav3os.nightly/tools/alpha_OSF1/alpha/acc/cc -I =
-I. =

-I.. -I../include -DIDENT=3DSABLE -DDEC2100_A500 -DSWAPTYPE=3D1 -DMACH -D=
OSF =

-DCOMPAT_43 -DUFS -DASE -DKERNEL -D_KERNEL -D_BSD -c vers.c
rm -f vmunix vmunix.sys
loading vmunix.sys
sh: 1076 Memory fault - core dumped
*** Exit 1 (ignored)
chmod 755 a.out
chmod: a.out: No such file or directory
*** Exit 4
Stop.
*** Exit 1
Stop.


I get the same sort of thing when I try 'build TLASER_vmunix' or =

'build MIKASA_vmunix'. As best I can tell, the 'ld' command that =

follows the '@${ECHO} loading $*.sys' line in the Makefile is what's
running when the shell throws up.

Any hints, clues, suggestions?

thanks,

-bill (DTN: 1-6177; http://www.zk3.dec.com/~grava/)
	If at first you DO succeed, try not to look astonished!