| Date Of Receipt: 26-AUG-1993 10:14:35.28
From: FLUME::"[email protected]" "Grant Van Dyck"
To: "Rich Larsen (908) 577-6083 DTN 462-6083 [email protected]" <[email protected]>
CC: [email protected], [email protected]
Subj: Re: tools dir in sandbox
Yes, BUT ...
( Warning: for use by professional hackers only - Kids, don't try this
at home!)
There are several environment variables that point to the tools space
and will need to be overridden in your sandbox to find your new tools.
In your sandbox's rc_files directory, create a file called custom. Here
are some sample contents which are correct for the Sterling stream.
# Local custom file
./local
replace setenv COMP_HOST_ROOT "${tools_base}/${cc_suite}"
replace setenv COMP_TARGET_ROOT "${tools_base}/${cc_suite}"
If you are not backed by minor, you'll want to grep these values from the
backing tree's rc_files and adjust accordingly, (ie. things like cc_suite
only exist in minor ... for now). Also this will require that you have
a full populated toolsdir in place. Try using mklinks for this, but you'll
need to be careful doing this to get the right links.
1) make sure that the directory
./sandbox/tools/alpha_OSF1/alpha/acc/usr/lib/cmplrs/cc
exists 1st.
2) from ./sandbox/tools/alpha_OSF1 do mklinks .
3) cd to ./sandbox/tools/alpha_OSF1/alpha/acc/usr/lib/cmplrs/cc
do mklinks . again.
4) remove the ld link and replace it with your own ld.
-Grant
|
| If I want to use a different `ld', do I just place it in the tools dir
| in my sandbox? What environment variable needs to be changed, if any,
| so I can use the one in tools dir in my sandbox?
|
| Thanks in advance,
|
| Rich
| ----------------------------------------------------------------
| Rich Larsen, M/S: UNX TCP/IP: [email protected]
| USSG/User Env. & Std. Group DECnet: UNXA::LARSEN
| Digital Equipment Corporation FAX: 908-577-6003
| 200 Route 9 North Voice: 908-577-6083
| Manalapan, New Jersey 07726 DTN: 462
|
|