Conference smurf::buildhelp

Date Of Receipt: 	27-JUL-1993 11:08:43.20
From: 	LOCORE::kate "Kate Baumgartner Lowrie USG"
To: 	locore::buildhelp
CC: 	locore::kate
Subj: 	build question

This is probably a build 101 question, but anyway ...
I'm trying to build a kernel for Sable, a new cpu.
I bcreate'd the new files, added them to the files
file, and edited the conf files (BINARY, and created
a SABLE conf file).  When I started the build in
my sandbox, I couldn't get the sable files to build.
I also noticed the files file in the obj directory
is not the same as my files file in my sandbox.
I'm backed by minor.bl4.  I don't really care what
I'm backed against at this point so I could easily
resb.

Any suggestions about what I may be doing wrong?

Thanks,
Kate

Date Of Receipt: 	23-SEP-1993 08:43:25.00
From: 	ABYSS::walker "Mary Walker"
To: 	abyss::buildhelp
CC: 	abyss::walker
Subj: 	build question

I just created a new sandbox backed to agosminor.nightly
I did the following
        workon
        mkdir -p usr/sbin/strsetup
        cd usr/sbin/strsetup
        build

My question is:
        should the executable I built be the same size/sum as
the executable in agosminor.nightly?
My executable is a different size and the one I build does not work
consistantly....

thanks for any help
mary walker

Date Of Receipt: 	23-SEP-1993 10:04:36.18
From: 	ABYSS::walker "Mary Walker"
To: 	abyss::buildhelp
CC: 	
Subj: 	re: build question

I have resolved my problem - but would still be interested in 
knowing why executable are a different size when you build them
in your sandbox than in the build tree...

mary

Date Of Receipt: 	23-SEP-1993 10:34:59.25
From: 	FLUME::"[email protected]" "Grant Van Dyck"
To: 	[email protected] (Mary Walker)
CC: 	[email protected]
Subj: 	Re: build question

| 
| I have resolved my problem - but would still be interested in 
| knowing why executable are a different size when you build them
| in your sandbox than in the build tree...
| 
| mary
| 

I believe this is because the relative path names inside the object are
different.  The version in nightly was actually built in agosminor.bld and 
copied (rdisted) to nightly. If you do an odump of the strings in
each version, you'll see the difference.

odump -vc strsetup

	-Grant

Date Of Receipt: 	23-SEP-1993 11:25:00.15
From: 	FLUME::jmcg "Jim McGinness"
To: 	[email protected], [email protected]
CC: 	
Subj: 	Re:  build question
> My question is: 	should the executable I built be the same size/sum as

 > the executable in agosminor.nightly?  My executable is a different
 > size and the one I build does not work consistantly....

I think the answer is: it *should*, if you compare stripped executables.
The unstripped executable contains date-stamped information.

 -- jmcg

Date Of Receipt: 	19-MAR-1996 12:38:28.72
From: 	SMURF::WASTED::schloss "Mike Schloss usg  19-Mar-1996 1235"
To: 	buildhelp@DEC:.zko.wasted
CC: 	
Subj: 	build question

I am running into a small problem and perhaps someone can explain
what I am seeing.  As part of the LSM project we are creating a new
library, both shared and non-shared.  A top down build of the entire
source tree causes the shared version to be built before the non-shared
version.  Unfortunately, the shared version depends upon the non-shared
version so one is found somewhere in the backing-tree/shared-sandbox.
Is this a known issue?  It looks to me like the PTOS nightly tree is
not built from a top-level build but is in fact built in a number of
steps with usr/ccs/lib being explicitly built before usr/shlib.  Is
this correct?  Does a clean (after removing obj and export trees)
top-down build risk getting stale shared libraries, or am I
misunderstanding something about the process?

Mike Schloss

Date Of Receipt: 	30-AUG-1996 11:27:07.95
From: 	HUNCH::"[email protected]" "Bruce Lutz USG"
To: 	[email protected]
CC: 	[email protected]
Subj: 	build question

I have modified a presto file pr.c which I want to include in the
generic vmunix.  I did the following:

    build BINARY_ MAKE_ARGS="presto.mod"

This worked fine to rebuild the presto.mod file.  How do I rebuild
GENERIC/vmunix?

Date Of Receipt: 	30-AUG-1996 12:26:26.97
From: 	SEAN::davidson "D. Sean Davidson"
To: 	[email protected], [email protected]
CC: 	[email protected]
Subj: 	Re:  build question

You should be able to do a

build GENERIC_relink

or

build GENERIC_vmunix


Check the http://nsa.zk3.dec.com/rengweb/ode/ page in the 'Code Development
and Testing' section for more information.


Sean

Date Of Receipt: 	17-OCT-1996 12:41:52.68
From: 	WASTED::jchang "Janice Chang USG"
To: 	buildhelp@DEC:.zko.wasted
CC: 	
Subj: 	build question

Hello.  I was wondering what cpu corresponds with the MUSTANG when
doing a kernel build?

Thanks!!

-Janice

Date Of Receipt: 	17-OCT-1996 14:29:04.89
From: 	FLUME::shashi "Shashi Mangalat USG  17-Oct-1996 1426"
To: 	Janice Chang USG <jchang@DEC:.zko.flume>
CC: 	buildhelp@DEC:.zko.flume
Subj: 	Re: build question

>Hello.  I was wondering what cpu corresponds with the MUSTANG when
>doing a kernel build?

AVANTI

--shashi