Conference smurf::buildhelp

417.0. "kernel build help needed" by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Thu Nov 04 1993 18:52

Date Of Receipt: 	 4-NOV-1993 17:51:01.10
From: 	WASTED::jmf "Joshua M. Friedman ULTRIX SDE  04-Nov-1993 1748"
To: 	buildhelp@wasted:zko.dec
CC: 	jones@dec:.zso.ulka
Subj: 	kernel build help needed

Can any kernel developers please help Alan with the attached problem?
thanks...		-josh

Alan - this is kind of an open forum, whoever is able to help...

-josh

------- Forwarded Message

Return-Path: [email protected] 
Delivery-Date: Thu, 04 Nov 93 16:17:42 -0500
Return-Path: [email protected]
Received: from wasted.zk3.dec.com by flambe.zk3.dec.com; 
(5.65/1.1.8.2/04Nov93-0154PM)
	id AA18557; Thu, 4 Nov 1993 16:17:40 -0500
Received: by wasted.zk3.dec.com; id AA15198; Thu, 4 Nov 1993 16:17:38 -0500
Date: Thu, 4 Nov 1993 16:17:37 -0500
Message-Id: <[email protected]>
From: [email protected] (F. Alan Jones)
To: [email protected]
Cc: jones, [email protected]
Subject: osf build problem

Hello Josh,

Tina Anderson forward this mail this morning to BUILDHELP.  Do you
happen to know who is working on a reply for me?  This problem,
combined with problems on our build server, has taken up the better
part of a week for me and I'd like to have some assurance that it
is being address by real-humans with real-dtn's.  I've seen no
acknowledgement thus far.

Thanks in advance,

Alan Jones
DTN 548-8531

- ---

Date: Thu, 4 Nov 1993 08:01:06 -0800
From: [email protected]
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: FWD: osf tree build ?

From:   RUST::decwet::jones    3-NOV-1993 17:20:47.43
To:     ode
CC:     stoppani, jones
Subj:   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


------- End of Forwarded Message

Date Of Receipt: 	 4-NOV-1993 18:19:17.42
From: 	ABYSS::"[email protected]" "Shashi Mangalat USG"
To: 	[email protected]
CC: 	[email protected]
Subj: 	Re: kernel build help needed

Assuming you have already created a sandbox backed by a recent agosminor
backing tree, the following will build a FLAMINGO kernel:

	% workon -sb your-sandbox-name 
	% cd kernel
	% build setup BINARY FLAMINGO

This will update header files and a few configuration dependant source
files in the object tree from the backing tree.  Arguments BINARY and
FLAMINGO will build the corresponding object trees and link a vmunix in
the FLAMINGO directory.  You can split those into three steps if you like.

The first time this will be a full build since you don't have any .o's
in your object tree.  From then on it should build only those targets
whose dependancies have changed.  (You can short cut it by tar'ing the
object tree over from the backing tree and just rebuilding the files
or configuration you want.)

You can omit the 'setup' if you don't expect the backing tree to change
after the initial build.  There are also faster ways to rebuild
depending on how much has changed since your first build.  If you have
changed only one source file you can just rebuild that .o and relink
manually, rather than letting make to search out the dependancies as it
may be slower due to the large number of files and dependancies.

Hope this helps.  Let me know if you need more info.  (DTN 381-2866)

--shashi