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

Conference vaxaxp::vmsnotes

Title:	VAX and Alpha VMS
Notice:	This is a new VMSnotes, please read note 2.1
Moderator:	VAXAXP::BERNARDO

Created:	Wed Jan 22 1997
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	703
Total number of notes:	3722

514.0. "Alpha and VAX differences" by CSC32::COMULADA () Wed Apr 23 1997 11:18

I have a customer who noted this problem. If he uses
an 'external long constant lnm%m_case_blind ' and
'lnm$_string' in his basic program, on the VAx it
compiles and links fine.
But ont he ALPHA, 6.2-1h3, and decbasic 1.2, he gets
a link error:

LINK-W-UDFSYM, 2 undefined symbols:
%LINK-I-UDFSYM,         LNM$M_CASE_BLIND
%LINK-I-UDFSYM,         LNM$_STRING
..

If we use the %INCLUDE, with basic$starlet.tlb, he 
gets no error, this is the workaround for now. 

Question: Any reason as to why it behaves this way on
the ALPHA??


Thanks,

Felix

T.R	Title	User	Personal Name	Date	Lines
514.1	Fix, Not Workaround...	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Wed Apr 23 1997 12:42`	30
	:If we use the %INCLUDE, with basic$starlet.tlb, he :gets no error, this is the workaround for now. This is the appropriate fix, not the workaround. I've found linking against images to resolve what should have been resolved via a symbol definition module -- CMS is one recent example -- can be hazardous. One spots missing symbols during compilation with the definition files -- one has to get to the LINK phase to resolve these otherwise. If the customer has symbols, then they can use SDL (on the freeware CD-ROM) and generate OpenVMS-like definitions, too. :Question: Any reason as to why it behaves this way on :the ALPHA?? Because the symbols were not made external in any shareable image module in IMAGELIB.OLB. (There are a few cases around where certain symbols were not made "external", and thus are not visible via the LINKER. You'll want to take a look at the VAX link map, and see where the symbol value was being resolved from...
514.2	Thanks for the info...	CSC32::COMULADA		`Mon Apr 28 1997 11:13`	8
	Any reason as to why some of the defs, like $prvdef are not included in basic$starlet. One has to create the macro and then link it to the program. Why aren't they included? Thanks, Felix
514.3	Contact BASIC Team	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Mon Apr 28 1997 11:18`	10
	Please contact the BASIC engineering team for further information and assistance -- the DEC C group has been working with OpenVMS engineering to get the C definitions handled in a more consistent fashion and included with the OpenVMS kit, for example. We (OpenVMS) can work with BASIC to create the include files using SDL, and can get these moved onto the kit. (If this is something that the customer and the BASIC team wishes to pursue.)
514.4	Thanks will check into it......	CSC32::COMULADA		`Mon Apr 28 1997 15:32`	0