[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | USG buildhelp questions/answers |
|
| Moderator: | SMURF::FILTER |
|
| Created: | Mon Apr 26 1993 |
| Last Modified: | Mon Jan 20 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2763 |
| Total number of notes: | 5802 |
363.0. "are we suporting the -sub_tree option to mksb?" by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Fri Oct 01 1993 15:53
Date Of Receipt: 1-OCT-1993 14:19:20.93
From: ABYSS::cande "Ed Cande USG"
To: abyss::odehelp
CC:
Subj: are we suporting the -sub_tree option to mksb?
I'm trying to use multiple backing trees to build part of DCE DFS.
I create my sandbox using the standard mksb, then do a workon into
that sandbox. Then I do mksb -back ALTDIR -sub_tree SUBDIR
for example:
mksb -back /project/dce/build/dfs.latest -sub_tree file
This creates everything correctly (project file, rc_files1, link1,
etc.). When I try to build, build/make does not use the backing tree
I specified but uses the backing tree from the original mksb. I've
tried doing a second workon, specifying the fileset for the file
directory (as created by the mksb/sub_tree command) and tried building
in the file subdirectory with the same results.
Any and all help is greatly appreaciated.
Thanks,
-- Ed
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 363.1 | RE: are we suporting the -sub_tree option to mksb? | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Mon Oct 04 1993 14:10 | 72 |
| Date Of Receipt: 4-OCT-1993 11:00:21.83
From: FLAMBE::"[email protected]"
To: MOLD::"[email protected]"
CC: flambe::odehelp
Subj: RE: are we suporting the -sub_tree option to mksb?
What were you originally backed to? I can try and recreate
your scenario if you can give me more information.
On flambe.zk3 I don't see /project/dce/build/dfs.latest.
What node has the /project/dce?
To debug this do a
workon -sb your-sandbox
more ../rc_files/project*
currentsb -back
cd file
currentsb -back
Which backing tree you instantiate on a "build"
is based on the rc_files/projects file,
and your current-working-directory.
**********************************************************
for example:
mksb -back ode3.0 josh (jo's sandbox)
workon -sb josh
mksb -back kerberos1.0 -sub_tree kerberos
more ../rc_files/projects
wet.zso.dec.com> more ../rc_files/proj*
/ode/local ../rc_files1/custom <---------- already had this sub-tree
/kerberos ../rc_files2/custom <---------- new one just created
wet.zso.dec.com> mksb -back kerberos1.0 -sub_tree kerberos
wet.zso.dec.com> currentsb -back
/usr/sde/disks/ode_ra2f/ode_builds/ode3.0
wet.zso.dec.com> cd kerberos
wet.zso.dec.com> currentsb -back
/usr/sde/disks/ode_ra4a/kerberos_build <------------ it changes by doing
a cd into the sub-tree.
wet.zso.dec.com> build
relative path: ./kerberos.
mkdir ../../obj/pmax_ultrix/kerberos
cd ../../obj/pmax_ultrix/kerberos
[ /kerberos/include ] <------------------- down in the kerberos tree
and build backed to kerberos
I also could of said
build export_all since I
just wanted some libraries.
makepath include/. && cd include && exec make MAKEFILE_PASS=FIRST build_all
include: created directory
^Cwet.zso.dec.com> cd .. <------ now that I got my kerberos
libraries and includes
build, I do a cd up into
my ode tree and start
building ode.
wet.zso.dec.com> build
relative path: ..
cd ../obj/pmax_ultrix
[ /ode ]
makepath ode/. && cd ode && exec make MAKEFILE_PASS=FIRST build_all
[ /ode/include ]
makepath include/. && cd include && exec make MAKEFILE_PASS=FIRST build_all
include: created directory
[ /ode/include/ode ]
makepath ode/. && cd ode && exec make MAKEFILE_PASS=FIRST build_all
|