| Title: | Languages | 
| Notice: | Speaking In Tongues | 
| Moderator: | TLE::TOKLAS::FELDMAN | 
| Created: | Sat Jan 25 1986 | 
| Last Modified: | Wed May 21 1997 | 
| Last Successful Update: | Fri Jun 06 1997 | 
| Number of topics: | 394 | 
| Total number of notes: | 2683 | 
    
    	I'm new to the world of C programming.  I've actually never
    taken a course in it.  Recently I copied about a dozen DECWindows
    example programs from the DW_EXAMPLES notesfile.  What I got was
    files with .C and .H extensions.  I didn't have a problem compiling
    the source code and I got the proper .OJB files.  My problems start
    when I try linking the object files to produce an executable.  I
    can't figure out which qualifiers to use with the link command in
    VMS.  The errors I get are usually similar:
    
    				. . . 
    
    first ->	   %LINK-I-UDFSYM,	XTSETVALUES
    
    				. . .
    
    then -> 	   %LINK-W-USEUNDEF, undefined symbol C$MAIN_ARGS referenced
    		           in psect $CODE offset %X00000006
    
    				. . .
    
    I'm totally stumped as to what these errors are trying to tell me. 
    Is there a way to 'read' the required LINK command parameters from
    these errors?  I've tried reading help under LINK and that
    information is clear only if you know C programming.
    
    	Any help appreciated,
    
    	Jim
    
    
    
    
    
| T.R | Title | User | Personal Name | Date | Lines | 
|---|---|---|---|---|---|
| 219.1 | Need the proper libraries | SARAH::PWONG | OS/2 Presentation Manager DECwrite | Fri Jan 20 1989 13:02 | 26 | 
|     RE: <<< Note 219.0 by ANARCY::DILIDDO "I'm not indecisive.......Am I?" >>>
    Jim,
    The BULOVA::DECWINDOWS conference is probably a better place for
    questions like yours but nonetheless, here are a few pointers:
    1) Make sure you have DECwindows properly installed on your system.
    2) Make sure you link with all the shareable libraries.  I have been
       using the following command file and have very little problem with
       it.  You might want to tailor the c$include logical to suit your
       particular needs.
	$ define/nolog c$include decw$examples,decw$include,sys$library
	$ define/nolog vaxc$include c$include
	$ cc 'p1/stand=port
	$ link/nomap 'p1,sys$input/opt
	sys$share:decw$dwtlibshr /share
	sys$share:decw$xlibshr /share
	sys$library:vaxcrtl /share
	sys$message:decw$xlibmsg /share
       Make sure you supply p1 when you @' the command file or submit it
       to a batch queue.
    - Paul
 | |||||
| 219.2 | Thanks | ANARCY::DILIDDO | I'm not indecisive.......Am I? | Fri Jan 20 1989 16:58 | 4 | 
|     
    	Thanks alot - that will help.
    
    	_Jim
 | |||||