[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference smurf::buildhelp

Title:USG buildhelp questions/answers
Moderator:SMURF::FILTER
Created:Mon Apr 26 1993
Last Modified:Mon Jan 20 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2763
Total number of notes:5802

2709.0. "need help with kernel build" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Wed Dec 04 1996 11:05

Date Of Receipt: 	 4-DEC-1996 11:02:03.42
From: 	ALPHA::dirce "Dirce Richards bos  04-Dec-1996 1058"
To: 	buildhelp@DEC:.zko.alpha
CC: 	
Subj: 	need help with kernel build

I am re-learning to build kernels, haven't done it for a year.
I am adding a new subsystem, called pps (pulse-per second).
I added it to the kernel/conf/files file.
I created pps_conf.c and modified a few other files. 
Now I am trying to build.

Today I did this:
	- resb steelos.bl5  (originally I was using steelos.nightly,
	which I learned that it is not a good idea when working on kernel)

	- build setup

	- tar'ed all the BINARY stuff into my space by doing:

% cd ./link/obj/alpha/kernel
% tar cf - BINARY [a-z]* | (cd /usr/sb/pps/obj/alpha/kernel/BINARY; tar xf - )

Now I am trying 
	
	build BINARY_

but it fails with

fast1<32> build BINARY_
relative path: ./kernel.
string passed to /usr/sde/osf1/build/steelos.bl5/tools/alpha_OSF1/alpha/hostbin/make:
   make -cF BINARY_ 
cd ../../obj/alpha/kernel
cd BINARY && make -cF  KCC=/usr/sde/osf1/build/steelos.bl5/tools/alpha_OSF1/alpha/acc/cc  LD=/usr/sde/osf1/build/steelos.bl5/tools/alpha_OSF1/alpha/acc/ld  CPP=cpp  AWK=awk  AR=/usr/sde/osf1/build/steelos.bl5/tools/alpha_OSF1/alpha/acc/ar  RANLIB='/usr/sde/osf1/build/steelos.bl5/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.bl5/tools/alpha_OSF1/alpha/acc/cc  -c -O2   -DLANGUAGE_C -warnprotos -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__digital__ -D__arch64__  -no_warnprotos -g3 ../../../../src/kernel/bsd/init_main.c
cc: Warning: ../../../../src/kernel/bsd/init_main.c, line 1254: In this statement, "(processor_t)0" of type "pointer to struct processor", is being converted to "long".
        first_thread->bound_processor = PROCESSOR_NULL;
--------^
objZ: No such file or directory - init_main.o

I actually re-did all steps above to make sure, but the error persists.

I hope one of you has a clue. Thanks,
	
	Dirce

T.RTitleUserPersonal
Name
DateLines
2709.1Re: need help with kernel buildAOSG::FILTERAutomatic Posting Software - mail to flume::puckWed Dec 04 1996 12:0662
Date Of Receipt: 	 4-DEC-1996 11:12:43.85
From: 	HUNCH::duane "Andrew Duane USG/PE"
To: 	[email protected] (dirce)
CC: 	buildhelp@DEC:.zko.hunch
Subj: 	Re: need help with kernel build

> I am re-learning to build kernels, haven't done it for a year.
> I am adding a new subsystem, called pps (pulse-per second).
> I added it to the kernel/conf/files file.
> I created pps_conf.c and modified a few other files. 
> Now I am trying to build.
> 
> Today I did this:
> 	- resb steelos.bl5  (originally I was using steelos.nightly,
> 	which I learned that it is not a good idea when working on kernel)
> 
> 	- build setup
> 
> 	- tar'ed all the BINARY stuff into my space by doing:
> 
> % cd ./link/obj/alpha/kernel
> % tar cf - BINARY [a-z]* | (cd /usr/sb/pps/obj/alpha/kernel/BINARY; tar xf - )
> 
> Now I am trying 
> 	
> 	build BINARY_
> 
> but it fails with
> 
> fast1<32> build BINARY_
> relative path: ./kernel.
> string passed to /usr/sde/osf1/build/steelos.bl5/tools/alpha_OSF1/alpha/hostbin/make:
>    make -cF BINARY_ 
> cd ../../obj/alpha/kernel
> cd BINARY && make -cF  KCC=/usr/sde/osf1/build/steelos.bl5/tools/alpha_OSF1/alpha/acc/cc  LD=/usr/sde/osf1/build/steelos.bl5/tools/alpha_OSF1/alpha/acc/ld  CPP=cpp  AWK=awk  AR=/usr/sde/osf1/build/steelos.bl5/tools/alpha_OSF1/alpha/acc/ar  RANLIB='/usr/sde/osf1/build/steelos.bl5/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.bl5/tools/alpha_OSF1/alpha/acc/cc  -c -O2   -DLANGUAGE_C -warnprotos -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__digital__ -D__arch64__  -no_warnprotos -g3 ../../../../src/kernel/bsd/init_main.c
> cc: Warning: ../../../../src/kernel/bsd/init_main.c, line 1254: In this statement, "(processor_t)0" of type "pointer to struct processor", is being converted to "long".
>         first_thread->bound_processor = PROCESSOR_NULL;
> --------^
> objZ: No such file or directory - init_main.o
> 
> I actually re-did all steps above to make sure, but the error persists.
> 
> I hope one of you has a clue. Thanks,

This seems to be that you have the file bsd/init_main.c checked out
in your local sandbox, and it is out of date with respect to the
backing tree's version.

For function prototypes, a *lot* of work was done to almost every
file to correct typedefs and prototypes. I would take a look at the
differences between your copy and the backing tree. A bmerge might
be in order.


-- 

Andrew L. Duane   DTN 381-1294		[email protected]
USG Kernel Scalability			alpha::duane
ZKO3-3/U14				www.zk3.dec.com/~duane


2709.2Re: need help with kernel buildAOSG::FILTERAutomatic Posting Software - mail to flume::puckWed Dec 04 1996 12:0730
Date Of Receipt: 	 4-DEC-1996 11:17:45.41
From: 	FLUME::johnf "John Flanagan USG Test Johnf Tools Group  04-Dec-1996 1113"
To: 	dirce@DEC:.zko.flume
CC: 	buildhelp@DEC:.zko.flume
Subj: 	Re: need help with kernel build

Which version of the files file did you use?   The one from steelos.nightly?
If that is the case, the problem is related to the function prototype work
that was done recently.   You're using the newer files file which has a 
stricter compiler flag on an older tree which has files that hadn't been
cleaned up yet.  What you really want to use is the BL6 tree, but it isn't
available yet.  I would suggest you switch to the nightly tree for the time
being.  The Fatal warning should go away then.

John
-- 


 ______________________________________________________________________

 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  
 ______________________________________________________________________