[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::decc

Title:DECC
Notice:General DEC C discussions
Moderator:TLE::D_SMITHNTE
Created:Fri Nov 13 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2212
Total number of notes:11045

1433.0. "DECC$$GA___CTYPET - Undefined symbol" by CSC32::J_HENSON (Don't get even, get ahead!) Wed Sep 06 1995 17:02

T.RTitleUserPersonal
Name
DateLines
1433.1RTL::COWANKen, TLGThu Sep 07 1995 10:4515
1433.2tyvmCSC32::J_HENSONDon't get even, get ahead!Thu Sep 07 1995 12:415
1433.3do you _need_ to copy DECC$SHR?UKARC1::WOOD_J"The information server either is not accessible or is refusing to serve the document to you"Tue Sep 26 1995 13:1816
1433.4RTL::COWANKen, TLGTue Sep 26 1995 16:228
1433.5CSC32::D_DERAMODan D'Eramo, Customer Support CenterTue Jul 30 1996 16:5213
1433.6.-1 sounds like a bugTAVENG::BORISBoris Gubenko, ISEWed Jul 31 1996 10:526
1433.7I've got good news and bad news...TLE::D_SMITHWed Jul 31 1996 14:5017
1433.8Consider Better Interface For Library Search...XDELTA::HOFFMANSteve, OpenVMS EngineeringFri Jan 10 1997 13:5810
1433.9Same problem, but could it get worse???CLARID::KREYERAndre KREYER, Sophia Antipolis (FR)Wed Mar 19 1997 11:3627
	I'm facing this very problem...
	
	I compile an image under OpenVMS for Alpha V7.1, DEC C V5.5-002
	and DECC$SHR X07.1-3. The object file is then moved onto other
	systems, where it gets linked.
	
	A user reported this Undefined DECC$$GL_CTYPET symbol while
	linking on a system running Alpha V6.1. I sort of understand
	the solution that's proposed (get the V6.1 DECC$SHR and compile
	against it), but this may not be the total answer to my case!

	Also note that the same .OBJ links fine on a Alpha V6.2 system
	running DECC$SHR T06.2-05...

	Question 1: should I worry about the same problem when running
		    against OpenVMS VAX (ie: is this problem Alpha
		    specific)?

	Question 2: my .OBJ may eventually end up on OpenVMS older than
		    6.1, what other problem could potentially surface?
		    What is the earliest version of DECC$SHR I should use
		    to guarantee the best coverage (ideally from Alpha V1.0
		    upwards if at all possible...)
	
	Thanks in advance for your help,			.Andre.

1433.10Pull Older RTLs Forward, Ship Images...XDELTA::HOFFMANSteve, OpenVMS EngineeringWed Mar 19 1997 12:5731
:	Question 1: should I worry about the same problem when running
:		    against OpenVMS VAX (ie: is this problem Alpha
:		    specific)?

   The DEC C compiler looks in the RTL to see what entry points are
   around, so yes, you have to worry about this on both platforms.

:	Question 2: my .OBJ may eventually end up on OpenVMS older than
:		    6.1, what other problem could potentially surface?
:		    What is the earliest version of DECC$SHR I should use
:		    to guarantee the best coverage (ideally from Alpha V1.0
:		    upwards if at all possible...)

   DIGITAL has been making a concerted effort to get folks upgraded
   off of OpenVMS Alpha V1.0, V1.5, and V1.5-1H1 -- the minimum version
   is OpenVMS Alpha V6.1.  (And I suspect you will not want to become
   entangled in the support issues for these older releases, too...)

   To "guarantee", you need to compile, link, test, and ship code built
   on OpenVMS Alpha V1.0 (or whateer is the oldest release you want to
   support).

   If you need back-support, I'd recommend pulling forward the RTLs,
   and LINK against the older RTLs.  (Back-shipping objects and LINKing
   on the customer system can be made to work, but I'd prefer to know
   more about the particular images the customer is running -- which
   means I prefer to avoid linking on the customer system.  Customers
   tend to do weird and unpredictable things with LNK$ logical names,
   with system library contents, with symbols for DCL commands, with
   weird logical names and directory structures, etc.)
1433.11TLE::D_SMITHDuane Smith -- DEC C RTLWed Mar 19 1997 14:188
    For both Alpha and VAX, I would recommend that you compile against an
    OpenVMS V6.1 DECC$SHR image.  The easiest way to obtain such beasts
    would be to grab the latest ECO kits off the web.
    
    Today the latest are ALPACRT09_061 and VAXACRT09_061.
    
    Duane
    
1433.12Beware Image GSMATCHXDELTA::HOFFMANSteve, OpenVMS EngineeringWed Mar 19 1997 14:3013
:    For both Alpha and VAX, I would recommend that you compile against an
:    OpenVMS V6.1 DECC$SHR image.  The easiest way to obtain such beasts
:    would be to grab the latest ECO kits off the web.
:    
:    Today the latest are ALPACRT09_061 and VAXACRT09_061.

  Duane, are you (hopefully) bumping the GSMATCH IDs?  If so, then grabbing
  the latest ECO kit won't work.  (One _does_ want to have these kits
  installed, but it's not clear if .0 wants to _require_ these kits.)
    
  If you do not have access to the necessary distribution kits, I or others
  can ship you copies of the "shipped-on-the-V6.1-kit" DECC$SHR images.