Conference smurf::buildhelp

Date Of Receipt: 	 2-MAR-1994 11:18:51.60
From: 	FLUME::"[email protected]" "Grant Van Dyck"
To: 	[email protected]
CC: 	[email protected]
Subj: 	Re: what good is populating my tools area?

Well, now that you've asked ...

The reason for populating the tools area is so that:

	A) Each user has a common toolset and isn't using an outdated
	   compiler.

	B) Each user doesn't have to expend 80-100 MB of space in each
	    sandbox for tools.


Now, that being said, if you WANTED to do that, it's very simple to setup.

1) Go into the tools area of your SB and do: mklinks -copy -over

2) Add a custom file to your rc_files that looks like this:


#
include ./local
replace setenv COFF_ACC_EXEC_PREFIX     "${tools_base}/acc/"
replace setenv COFF_GCC_EXEC_PREFIX     "${tools_base}/gcc/"
replace setenv COFF_MCC_EXEC_PREFIX     "${tools_base}/mcc/"
replace setenv COMP_HOST_ROOT           "${tools_base}/${cc_suite}"
replace setenv COMP_TARGET_ROOT         "${tools_base}/${cc_suite}"
replace setenv TARGET_EXEC_PREFIX       "${tools_base}/hostbin/"


Do another workon and then see what happens. However you may have
to wait til buffer comes back up - again :-)  

Sorry for the inconvienience.


	-Grant
| Our makefiles seem to be wired up with absolute pathnames that start with /us
r/sde...
| 
| So what good does it do to populate the tools area of a sandbox?  It would ap
pear
| that the local tools won't get used, so there's no speed advantage and we're
| still dependent upon (and at the mercy of) the servers.
| 
| 
| 	-- Farrell
| 

Date Of Receipt: 	 2-MAR-1994 11:38:53.04
From: 	MINSRV::ftw "Farrell Woods USG"
To: 	Grant Van Dyck <minsrv::vandyck>
CC: 	minsrv::odehelp
Subj: 	Re: what good is populating my tools area?
> The reason for [not?] populating the tools area is so that: 	

> 
> 	A) Each user has a common toolset and isn't using an outdated
> 	   compiler.

A definite risk.  But if we were to pay attention to the daily build mail, they call
out the version of the compiler kit used.  So if we noticed that that had changed,
we could do a mklinks -copy -over ...  Right?  Still a risk though if we were to
get out of sync.

> 	B) Each user doesn't have to expend 80-100 MB of space in each
> 	    sandbox for tools.

I'm lucky enough to have a bit of spare disk.  I kick off my own build each evening,
plus I tend to build odds and ends of files throughout the day as I tinker with
my drivers and such.  So having local everything means:

	o My builds go faster

	o I'm not using as much net bandwidth

 

> 2) Add a custom file to your rc_files that looks like this:

This is the info I needed.  Thanks!  BTW I'm not sure where I could have looked
(in doc. terms) to get this info.  Any pointers, or is it kinda "word of mouth"?


> Sorry for the inconvienience.

Sigh.  Not your fault.


	-- Farrell

Date Of Receipt: 	 2-MAR-1994 14:49:41.35
From: 	MINSRV::ftw "Farrell Woods USG"
To: 	Grant Van Dyck <minsrv::vandyck>
CC: 	[email protected], minsrv::janet
Subj: 	Re: what good is populating my tools area?
I'm having lots of trouble using local tools.  For instance, instead of this: 	

#
include ./local
replace setenv COFF_ACC_EXEC_PREFIX     "${tools_base}/acc/"
replace setenv COFF_GCC_EXEC_PREFIX     "${tools_base}/gcc/"
replace setenv COFF_MCC_EXEC_PREFIX     "${tools_base}/mcc/"
replace setenv COMP_HOST_ROOT           "${tools_base}/${cc_suite}"
replace setenv COMP_TARGET_ROOT         "${tools_base}/${cc_suite}"
replace setenv TARGET_EXEC_PREFIX       "${tools_base}/hostbin/"

I had to create a custom file that looked like this:

#
include ./local
replace setenv COFF_ACC_EXEC_PREFIX     "${tools_base}/../alpha_OSF1/alpha/acc/"
replace setenv COFF_GCC_EXEC_PREFIX     "${tools_base}/../alpha_OSF1/alpha/gcc/"
replace setenv COFF_MCC_EXEC_PREFIX     "${tools_base}/../alpha_OSF1/alpha/mcc/"
replace setenv COMP_HOST_ROOT           "${tools_base}/../alpha_OSF1/alpha/${cc_suite}"
replace setenv COMP_TARGET_ROOT         "${tools_base}/../alpha_OSF1/alpha/${cc_suite}"
replace setenv TARGET_EXEC_PREFIX       "${tools_base}/../alpha_OSF1/alpha/hostbin/"


Then the next hurdle is that mklinks doesn't appear to preserve file permissions
properly:

1.82 marvin:ftw> build FLAMINGO_vmunix
relative path: ./kernel.
cd ../../obj/alpha/kernel
cd FLAMINGO && make -cF  KCC=/x3/sandboxes/alphabox/tools/alpha/../alpha_OSF1/alpha/acc/cc  LD=/x3/sandboxes/alphabox/tools/alpha/../alpha_OSF1/alpha/acc/ld  CPP=cpp  AWK=awk  AR=/x3/sandboxes/alphabox/tools/alpha/../alpha_OSF1/alpha/acc/ar  RANLIB='/x3/sandboxes/alphabox/tools/alpha/../alpha_OSF1/alpha/acc/ar ts'  SHELL=sh  SED=sed  SORT=sort  ECHO=echo  KSH=ksh  EGREP=egrep  GREP=grep  LINT=lint CONFIG=FLAMINGO vmunix
/x3/sandboxes/alphabox/tools/alpha/../alpha_OSF1/alpha/acc/cc  -c -O2 -g3  -DLANGUAGE_C -g3 -G 4 -I -I. -I.. -I../include -DIDENT=FLAMINGO -DDEC3000_500 -DSWAPTYPE=1 -DMACH -DOSF -DCOMPAT_43 -DUFS -DTRN -DKERNEL -D_KERNEL -D_BSD -signed  -no_excpt -Wb,-static -Wco,-nofloat -Olimit 1500 -D__alpha -Umips -UMIPS ../kern/lockinfo.c
sh: /x3/sandboxes/alphabox/tools/alpha/../alpha_OSF1/alpha/acc/cc: cannot execute
*** Exit 1
Stop.
*** Exit 1
Stop.
1.83 marvin:ftw> ls -l /x3/sandboxes/alphabox/tools/alpha/../alpha_OSF1/alpha/acc/cc
-rw-r--r--   1 ftw      system    331584 Jan 11 17:07 /x3/sandboxes/alphabox/tools/alpha/../alpha_OSF1/alpha/acc/cc



Something dropped the execute permission bit.

Date Of Receipt: 	 2-MAR-1994 15:35:00.97
From: 	FLUME::"[email protected]" "Grant Van Dyck"
To: 	[email protected]
CC: 	Grant Van Dyck    <[email protected]>, [email protected],
	[email protected]
Subj: 	Re: what good is populating my tools area?
| I'm having lots of trouble using local tools.  For instance, instead of this: 	

| 
| #
| include ./local
| replace setenv COFF_ACC_EXEC_PREFIX     "${tools_base}/acc/"
| replace setenv COFF_GCC_EXEC_PREFIX     "${tools_base}/gcc/"
| replace setenv COFF_MCC_EXEC_PREFIX     "${tools_base}/mcc/"
| replace setenv COMP_HOST_ROOT           "${tools_base}/${cc_suite}"
| replace setenv COMP_TARGET_ROOT         "${tools_base}/${cc_suite}"
| replace setenv TARGET_EXEC_PREFIX       "${tools_base}/hostbin/"
| 
| I had to create a custom file that looked like this:

Do sbinfo tools_base and see what you get.

you could add the line 
 replace tools_base  ${sandbox_base}/tools
after the include ./local line



| 
| #
| include ./local
| replace setenv COFF_ACC_EXEC_PREFIX     "${tools_base}/../alpha_OSF1/alpha/ac
c/"
| replace setenv COFF_GCC_EXEC_PREFIX     "${tools_base}/../alpha_OSF1/alpha/gc
c/"
| replace setenv COFF_MCC_EXEC_PREFIX     "${tools_base}/../alpha_OSF1/alpha/mc
c/"
| replace setenv COMP_HOST_ROOT           "${tools_base}/../alpha_OSF1/alpha/${
cc_suite}"
| replace setenv COMP_TARGET_ROOT         "${tools_base}/../alpha_OSF1/alpha/${
cc_suite}"
| replace setenv TARGET_EXEC_PREFIX       "${tools_base}/../alpha_OSF1/alpha/ho
stbin/"
| 
| 
| Then the next hurdle is that mklinks doesn't appear to preserve file permissi
ons
| properly:

| 
| 
| Something dropped the execute permission bit.
| 

As I said - try rdist. 1st remove all but the top level (tools) in your
SB.

	-Grant

Date Of Receipt: 	 2-MAR-1994 15:43:51.86
From: 	MINSRV::ftw "Farrell Woods USG"
To: 	Grant Van Dyck <minsrv::vandyck>
CC: 	[email protected], Grant Van Dyck    <[email protected]>,
	[email protected], [email protected]
Subj: 	Re: what good is populating my tools area?

> As I said - try rdist. 1st remove all but the top level (tools) in your
> SB.

Okay, I'll bite:

0.49 marvin:ftw> priv rdist -Rwc tools marvin:/x3/sandboxes/alphabox
updating host marvin
tools: no password entry for uid 8887
tools/alpha_OSF1: no password entry for uid 8887
installing: tools/alpha_OSF1
tools/alpha_OSF1/alpha: no password entry for uid 8887
installing: tools/alpha_OSF1/alpha
tools/alpha_OSF1/alpha/hostbin: no password entry for uid 8887
installing: tools/alpha_OSF1/alpha/hostbin
tools/alpha_OSF1/alpha/hostbin/ctab: no password entry for uid 8887
installing: tools/alpha_OSF1/alpha/hostbin/ctab
tools/alpha_OSF1/alpha/hostbin/gencat: no password entry for uid 8887
installing: tools/alpha_OSF1/alpha/hostbin/gencat
tools/alpha_OSF1/alpha/hostbin/mig: no password entry for uid 8887
.....

Date Of Receipt: 	 2-MAR-1994 15:54:39.95
From: 	FLUME::"[email protected]" "Grant Van Dyck"
To: 	[email protected]
CC: 	[email protected], [email protected]
Subj: 	Re: what good is populating my tools area?
I never said this would be EASY: 	-)

It's not what we'd call recommended procedure, so ... two choices,

add a local devbld (8887) entry in you passwd file
chown -R ftw:staff tools   when you're done.

Your choice.


	-Grant


| 
| > As I said - try rdist. 1st remove all but the top level (tools) in your
| > SB.
| 
| Okay, I'll bite:
| 
| 0.49 marvin:ftw> priv rdist -Rwc tools marvin:/x3/sandboxes/alphabox
| updating host marvin
| tools: no password entry for uid 8887
| tools/alpha_OSF1: no password entry for uid 8887
| installing: tools/alpha_OSF1
| tools/alpha_OSF1/alpha: no password entry for uid 8887
| installing: tools/alpha_OSF1/alpha
| tools/alpha_OSF1/alpha/hostbin: no password entry for uid 8887
| installing: tools/alpha_OSF1/alpha/hostbin
| tools/alpha_OSF1/alpha/hostbin/ctab: no password entry for uid 8887
| installing: tools/alpha_OSF1/alpha/hostbin/ctab
| tools/alpha_OSF1/alpha/hostbin/gencat: no password entry for uid 8887
| installing: tools/alpha_OSF1/alpha/hostbin/gencat
| tools/alpha_OSF1/alpha/hostbin/mig: no password entry for uid 8887
| .....

Date Of Receipt: 	 2-MAR-1994 16:03:40.98
From: 	MINSRV::ftw "Farrell Woods USG"
To: 	Grant Van Dyck <minsrv::vandyck>
CC: 	[email protected], [email protected]
Subj: 	Re: what good is populating my tools area?

I thought some other machine was griping about the missing uid entry...  Now the
rdist has run.  I'll go back and see if I can do local builds again.

> It's not what we'd call recommended procedure...

But I thought the whole idea of populating the tools area (via mkinks or whatever)
was for the expressed purpose of being pretty much self-hosted (backing trees and
the b* commands excepted, unless you've got *lots* of room).  Why bother with
the feature then?


Look I'm not trying to be a trouble-maker.  I just want things to go faster. :-)

Date Of Receipt: 	 2-MAR-1994 16:09:10.92
From: 	FLUME::"[email protected]" "Grant Van Dyck"
To: 	[email protected]
CC: 	[email protected], [email protected]
Subj: 	Re: what good is populating my tools area?

| But I thought the whole idea of populating the tools area (via mkinks or what
ever)
| was for the expressed purpose of being pretty much self-hosted (backing trees
 and
| the b* commands excepted, unless you've got *lots* of room).  Why bother with
| the feature then?
| 
| 
| Look I'm not trying to be a trouble-maker.  I just want things to go faster. 
:-)
| 


I just told you how to do it because you wanted to know. It is possible,
but as I said, not necessarily recommended, because the enviroment is
set up, intentionally to use a single set of tools.

	-Grant