Conference smurf::buildhelp

413.0. "FWD: osf tree build ?" by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Thu Nov 04 1993 11:20

Date Of Receipt: 	 4-NOV-1993 11:01:02.13
From: 	ABYSS::decwet::anderson
	RUST::decwet::jones    3-NOV-1993 17:20:47.43
To: 	abyss::buildhelp
	ode
CC: 	abyss::jones, abyss::ode, abyss::stoppani
	stoppani, jones
Subj: 	FWD: osf tree build ?
	osf tree build ?
The traditional kernel build involves 2 phases: 	

1) config & depend that create a Makefile in your "systemname" directory
2) make all to build *.o files and link vmunix


What I understand of the "build /src/kernel/setup" command is that 
it accomplishes phase 1 above.  However, after running "build setup"
it seems that *all* *.o files are regarded as out of date and re-compiled
by "build BINARY".  Once the dependencies are established in the Makefile,
make *should* be able to determine which *.o files need to be rebuilt
and only re-compile those *.o's.  This was the case under the original
UNIX kernel build environment.  My questions are:

What is the latest fokelore on the expected behavior of "build setup"?
Can a config/depend that doesn't outdate *.o be accomplished?
Who created the OSF build environment, and what were their intentions
  regarding the behavior of "build setup"?

Thanks,

Alan