Conference turris::decc

2125.0. "DECC$$Gx___CTYPEx undefined at link time" by PRSSOS::VOUTERS (Philippe VOUTERS, Evry (France)) Fri Mar 21 1997 09:54

    Hello,
    
    When linking third party object modules on their ALPHA OVMS V6.2, a
    customer gets the following undefined symbols. Looking at MOSAIC,
    I noticed some discussions about DECC$$GA___CTYPE but not with these
    two symbols. Where could they come from ? How to resolve these sym-
    bols ? The customer is using RDB/VMS or Oracle SGDB.
    Thank you for any hints.
    Best regards,
    Philippe Vouters (MCS France)
    
 - Linking ASADMURG.EXE
%LINK-W-NUDFSYMS, 2 undefined symbols:
%LINK-I-UDFSYM,  DECC$$GA___CTYPET 
%LINK-I-UDFSYM,  DECC$$GL___CTYPEA 
%LINK-W-USEUNDEF, undefined symbol DECC$$GL___CTYPEA referenced   in psect $LINK
$ offset %X000009F8   in module P file DKB0:[PRODUIT.SEDIT.AS]LIBP.OLB;1
%LINK-W-USEUNDEF, undefined symbol DECC$$GA___CTYPET referenced   in psect $LINK
$ offset %X00000A00   in module P file DKB0:[PRODUIT.SEDIT.AS]LIBP.OLB;1

    I have forward your problem to a C RTL developer.  Your problem looks
    similiar to the one in note 1214.5, which leads me to a couple of
    questions:
    
       1)  What version of the operating system were the third party
           objects built on?
    
       2)  Does your customer define DECC$SHR prior to linking his
    	   application?  (What I am trying to find out is if your 
    	   customer is building against the 6.1 version of DECC$SHR.)
    
    Linda.

    RE : .1
    
    The version of OpenVMS AXP is V6.1 and the P module has been developped
    by a third-party software supplier on OpenVMS AXP V6.2.
    The DECC$SHR.EXE from an OpenVMS AXP V6.2 containing definitions for
    these 2 symbols has been copied to the customer system who defined
    the DECC$SHR symbol for both link and run time. The result is totally
    satisfying for the customer.
    Best regards,
    Philippe