Conference smurf::buildhelp

    Date: Tue, 27 Apr 1993 11:18:49 -0400
    From: jmcg (Jim McGinness)
    To: [email protected], [email protected], [email protected]
    Subject: Re:  Make Question
    
    You ask a hard question.  The ODE make is being used because it works
    appropriately in the ODE environment whereas the POSIX-make wouldn't.
    By insisting on POSIX-make, I believe you have to give up all the work
    that's gone into the usr/lib/makefiles/*.mk or at least buy into
    extensive adaptation work.
    
    	-- jmcg
    
    

    Date: Tue, 27 Apr 1993 13:17:59 -0400
    Message-Id: <[email protected]>
    From: [email protected] (Kim Peterson, DECwest Engineering)
    To: [email protected]
    Cc: [email protected]
    Subject: RE: Make Question
    
    This is a buildhelp question.
    
    What is your project trying to build?
    1) If it is trying to build DEC/OSF1 source, you must use the DEC/OSF1 make
    (The distinction between the make that DEC/OSF1 uses and the make
    provided by ODE is important to make)
    2) If it is trying to build new sources, then using the POSIX make is
    feasible (Which POSIX make are you using? The one provided by OSF, or the 
    one provided by DEC/OSF1?  They are different.  There are actually four 
    makes that are associated with OSF/1, and you need to be clear on which 
    one of these four you should be using).  The errors you are getting look 
    like they are coming from an OSF provided make, and not the POSIX make 
    provided by DEC/OSF1 (which is, I think, /usr/opt/ultrix/usr/bin/make)
    --Kim

    To: [email protected]
    Cc: [email protected], [email protected]
    Subject: Re: Make Question 
    In-Reply-To: Your message of "Tue, 27 Apr 93 10:43:43 EDT."
                 <[email protected]> 
    Date: Tue, 27 Apr 93 13:01:02 EDT
    From: Grant Van Dyck <vandyck>
    
    
    I'm missing some info here, but I'll try to explain in general how make
    works in ode and which make is used.
    
    When the build runs (or you build in a sandbox) it uses a non-shared
    version of the standard make (not the ODE make - ie
    /usr/sde/tools/platform/bin/make -which is based on OSF 1.1) and it 
    finds it in ./tools/alpha/cc/usr/bin for the maintenance release and 
    ./tools/alpha_OSF1/alpha/hostbin for the minor release.
    
    I assume that you are getting these errors when you do a workon
    otherwise you wouldn't get the error about "No such directory: ../obj".
    make looks for the environment variable OBJECTDIR and if it finds it,
    wants to build/write there. When you are in a workon this is set.
    
    Secondly, when you are in a workon, you PATH gets reset - at least as
    faras build/make are concerned - but not shell, so whatever you put in
    your shell PATH is irrelevant.  To find out what your sandbox PATH is, do
    the following:
    
    sbinfo PATH
    
    and while you're at it do an: sbinfo OBJECTDIR
    
    you should get what you got 
    polaris minor/src [20] sbinfo OBJECTDIR
    ../obj/alpha
    
    this path is relative to your SOURCEBASE. The directory ../obj/alpha
    must exist and be writeable by you.  If you do not want this behavior for
    your environment, then you need to fix the rc_files for your backing tree
    to unsetenv OBJECTDIR and correctly define PATH to get the make you
    desire.
    
    
    		-Grant
    
    
            

    Delivery-Date: Tue, 27 Apr 93 13:20:23 -0400
    Return-Path: [email protected]
    Received: by flume.zk3.dec.com (5.65/DEC-USSG-ZK3-ULTRIX-09/27/91);
    	id AA22871; Tue, 27 Apr 1993 13:20:08 -0400
    Received: by krisis.zk3.dec.com (5.65/DEC-USSG-ZK3-ULTRIX-09/27/91);
    	id AA11849; Tue, 27 Apr 1993 13:19:20 -0400
    Message-Id: <[email protected]>
    To: Grant Van Dyck <[email protected]>
    Cc: [email protected], [email protected], [email protected],
            [email protected]
    Subject: Re: Make Question 
    In-Reply-To: Your message of "Tue, 27 Apr 93 13:01:02 EDT."
                 <9304271701.AA16927@polaris> 
    Date: Tue, 27 Apr 93 13:19:19 -0400
    From: [email protected]
    X-Mts: smtp
    
    
    
    Hi,
    
    Thanks, you were correct, I needed to unsetenv OBJECTDIR.
    

Date Of Receipt: 	13-FEB-1995 11:19:29.96
From: 	SMURF::QUARRY::"[email protected]" "13-Feb-1995 1118"
To: 	russell@dec:.shr.subsys (I'm trapped! 13-Feb-1995 0914)
CC: 	[email protected]
Subj: 	Re: ODE
Do you have web access?  If so try: 	
http: 	//nsa.zk3.dec.com/rengweb
If not you should contact the ODE group at DEC West - DECWET: 	:ODE

	-Grant

| Hi,
| 
| 	I'm doing development under OSF.  I'm about to put OSF onto my Jensen. 
 
| I'm looking for documentation on how to use it and how to install it on my 
| system.
| 
| Thanks,
| Frank Russell
| DTN 237-6543
| 
| 

Date Of Receipt: 	27-DEC-1995 16:10:44.68
From: 	SMURF::FLUME::darcy "Maryellen Darcy DIGITAL UNIX PUBLICATIONS"
To: 	odehelp@DEC:.zko.flume
CC: 	darcy@DEC:.zko.flume
Subj: 	ODE

Hi,

I can't seem to get into a workon where I can use the ODE services (bco, blog,
etc.).  These are the commands I typed along with the output I got:

Thanks!

toastd> odepath
toastd> ki
Kerberos Initialization for "Maryellen_Darcy"
Password:
toastd> klist
Ticket file:    /var/dss/kerberos/tkt/tkt1241
Principal:      Maryellen_Darcy@ZONE

  Issued           Expires          Principal
Dec 27 16:00:18  Dec 28 02:00:18  krbtgt.ZONE@ZONE
toastd> workon -sb plat_ref
cd'ing to sandbox source directory: /home/darcy/sandbox/plat_ref/src.
starting new shell: /bin/csh.
To access your ODE server you must:

        o kinit $PRINCIPAL (then input your kerberos password)

        o Enter workon -sb sandbox name or default.

Please obtain kerberos ticket and try again.


NOTE: You are in your sandbox.

   o This sandbox can only be used for ODE services which don't
   require the ODE server (i.e. build, mklinks, etc. ).
   To avoid this message use the no kerberos switch:

          workon -nk -sb sandbox name

Date Of Receipt: 	27-DEC-1995 18:21:27.26
From: 	SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE"
To: 	darcy odehelp
CC: 	
Subj: 	Re:  ODE

Mark Angel came by and we suspect that your problem is that your system
time has drifted more than the 5 minutes allowed by Kerberos.

-josh

Date Of Receipt: 	26-FEB-1996 14:53:43.36
From: 	SMURF::ALPHA::frank "Douglas Frank USG  26-Feb-1996 1450"
To: 	odehelp@DEC:.zko.alpha
CC: 	
Subj: 	make

I can't seem to gat make to understand the conditional syntax of ".if"
as explained on the odeman page.

.if defined ${var}
 ...
.endif

produces "Must be a separator on line ..."

I can't see what I'm doing wrong.  I set up my path to find make in
/usr/sde/tools/alpha_OSF1/bin (just to be sure) but that didn't help

thanks
-- 

--Doug

Date Of Receipt: 	26-FEB-1996 15:10:08.83
From: 	SMURF::FLUME::"[email protected]" "Grant Van Dyck  26-Feb-1996 1506"
To: 	[email protected]
CC: 	[email protected]
Subj: 	Re: make

Wrong make. The OS and X builds use the make from the OS pool - 
/usr/ccs/bin/make

The "ode" make is used to build ODE - currently, and a couple of other things.

Try man make.


| I can't seem to gat make to understand the conditional syntax of ".if"
| as explained on the odeman page.
| 
| .if defined ${var}
|  ...
| .endif
| 
| produces "Must be a separator on line ..."
| 
| I can't see what I'm doing wrong.  I set up my path to find make in
| /usr/sde/tools/alpha_OSF1/bin (just to be sure) but that didn't help
| 
| thanks
| -- 
| 
| --Doug
| 
| 

-- 

				-Grant

Date Of Receipt: 	27-FEB-1996 16:01:48.79
From: 	SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE  27-Feb-1996 1558"
To: 	frank@DEC:.zko.flume
CC: 	[email protected]
Subj: 	Re: make

Doug, more information about differences between our make & ode make can
be found in
	/usr/sde/osf1/doc/makefile-notes

The only conditional mechanism available is the in-line macro substitution
documented in the Digital UNIX "man make" reference page:

    $(MACRO?string1:string2)

-josh