topic Re: C++ LINK Issue in Operating System - OpenVMS

C++ LINK Issue

Vince M. Kostoff — Thu, 21 Feb 2008 14:46:48 GMT

Upgrade from DEC C++ V5.3-005 to HP C++ V7.3-009 getting undefined symbols on code developed, not HP C++. On the surface the old system to new system looks similar. Upgraded OS revision as well. 6.2 to 8.3 OpenVMS.

Why?
Hints where to look?
Changes in CXXLINK causing?
Demangling/Mangling?

Re: C++ LINK Issue

Steven Schweda — Thu, 21 Feb 2008 15:07:29 GMT

> Hints where to look?

First, a VMS forum would be a better place
than this HP-UX forum.

http://forums.itrc.hp.com/service/forums/familyhome.do?familyId=288

An actual error message or two might be
useful, too. Did you re-compile everything
on the new OS with the new compiler?

Re: C++ LINK Issue

John Gillings — Thu, 21 Feb 2008 21:50:32 GMT

Vince,

You'll need to show your compile and link commands and exact text of any resulting error messages. In theory you should be able to link modules compiled with different versions of the compiler, but in practice, C++ mangling might be getting in the way.

It's a good habit to always compile with maximum listings - /LIST/SHOW=ALL or the language specific equivalent, then LINK/MAP/FULL/CROSS. That should help locate any problems.

Re: C++ LINK Issue

Robert Gezelter — Thu, 21 Feb 2008 22:48:32 GMT

Vince,

I agree with John. Should is the operative word. Full listings help. Crossing out the modules that resolve correctly will identify precisely what is happening.

I would start with demangling the unresolved symbols and checking if the declarations are correct, having seen problems similar to this in the past with various situations.

- Bob Gezelter, http://www.rlgsc.com

Re: C++ LINK Issue

Vince M. Kostoff — Fri, 22 Feb 2008 16:41:01 GMT

$ CXXLINK /log /TRACE/DEBUG/NOMAP/EXEC=exe_tools:SDDVIEW.EXE sys$share:libcxxstd/INCL=CXXL_STD_INIT, here:sddview.opt/opt, SDDVIEW.OBJ, SDDVIEW_SMG.OBJ, UTL_SYSF_ITERATE.OBJ, RTNSDFI_UTIL.OBJ
%CXXLNK-I-LNKLIB_NAME, LNK$LIBRARY_3 defined as follows:

$ DEFINE LNK$LIBRARY_3 SYS$LIBRARY:LIBCXXSTD
%CXXLNK-I-LNKLIB_NAME, LNK$LIBRARY_2 defined as follows:

$ DEFINE LNK$LIBRARY_2 MILL_SHRLIB
%CXXLNK-I-LNKLIB_NAME, LNK$LIBRARY_1 defined as follows:

$ DEFINE LNK$LIBRARY_1 MILL_GPT4000LIB
%CXXLNK-I-LNKLIB_NAME, LNK$LIBRARY defined as follows:

$ DEFINE LNK$LIBRARY MILL_SDDLIB
%CXXLNK-I-LINKCOM, Link command:

link /TRACE/DEBUG/NOMAP/EXEC=EXE_TOOLS:SDDVIEW.EXE SYS$SHARE:LIBCXXSTD/INCL=CXXL_STD_INIT,HERE:SDDVIEW.OPT/OPT,SDDVIEW.OBJ,SDDVIEW_SMG.OBJ,UTL_SYSF_ITERATE.OBJ,RTNSDFI_UTIL.OBJ /NOEXEC/NOMAP/NOCROS/NOFULL/NOBRIE/NODEBU/INFORM

%CXXLNK-I-OBJFILE, Looking for object file: SYS$DISK:[.CXX_REPOSITORY]CXX$ADDRRRSXNQ13STD41BSC0KL9U2H.obj
%CXXLNK-I-OBJFILE, Looking for object file: SYS$DISK:[.CXX_REPOSITORY]CXX$DSPLYHADRXNQ13STD41B3ES1J3I.obj
%CXXLNK-I-OBJFILE, Looking for object file: SYS$DISK:[.CXX_REPOSITORY]CXX$UPDTDSPLYXNQ13STD41B34GGI49.obj
%CXXLNK-I-OBJFILE, Looking for object file: SYS$DISK:[.CXX_REPOSITORY]CXXL$CTQ13STD42BSCFSTRAM11JGA8S.obj
%CXXLNK-I-ADDOPT, Adding SYS$DISK:[.CXX_REPOSITORY]CXXL$CTQ13STD42BSCFSTRAM11JGA8S.obj to linker options file
%CXXLNK-I-OBJFILE, Looking for object file: SYS$DISK:[.CXX_REPOSITORY]CXXL$DTQ13STD42BSCFSTRAM1KJFVB3.obj
%CXXLNK-I-ADDOPT, Adding SYS$DISK:[.CXX_REPOSITORY]CXXL$DTQ13STD42BSCFSTRAM1KJFVB3.obj to linker options file
%CXXLNK-I-OBJFILE, Looking for object file: SYS$DISK:[.CXX_REPOSITORY]CXXL$GTLNQ13STD41BSCSTRA1ASRBQ4.obj
%CXXLNK-I-ADDOPT, Adding SYS$DISK:[.CXX_REPOSITORY]CXXL$GTLNQ13STD41BSCSTRA1ASRBQ4.obj to linker options file
%CXXLNK-I-OBJFILE, Looking for object file: SYS$DISK:[.CXX_REPOSITORY]CXXL$LSQ13STD41BSCSTRAMC19219UE.obj
%CXXLNK-I-ADDOPT, Adding SYS$DISK:[.CXX_REPOSITORY]CXXL$LSQ13STD41BSCSTRAMC19219UE.obj to linker options file
%CXXLNK-I-OBJFILE, Looking for object file: SYS$DISK:[.CXX_REPOSITORY]CXXL$RSXNQ13STD41BSCSTRA0HUVKVV.obj

It seems like after the /inform in the OLD system, it would read ,SYS$LIBRARY:LIBCXXSTD.OLB/LIB

Re: C++ LINK Issue

Craig A Berry — Fri, 22 Feb 2008 18:17:38 GMT

5.3 to 7.3 is a big jump. I suggest reading the release notes carefully. IIRC there were big changes in C++ between the 5.x and 6.x eras. You can find the release notes here:

http://h71000.www7.hp.com/commercial/cplus/alpha_doc/rnv.html

Re: C++ LINK Issue

Arch_Muthiah — Wed, 27 Feb 2008 23:22:28 GMT

Vince,

Make sure you have demangler database. and include /Repository=disk:[..cxx_rep..],
you problem will be solved.

see $help cxx /repo and $help cxxlink/repo

Archie

Re: C++ LINK Issue

Vince M. Kostoff — Mon, 03 Mar 2008 19:04:12 GMT

Now I get undefined symbol for the following:

%LINK-I-UDFSYM, std::basic_istream > &operator>>(std::basic_istream > &, String &)

Re: C++ LINK Issue

Vince M. Kostoff — Mon, 21 Apr 2008 17:32:33 GMT

Thanks to all for providing hints. I realize my notes may not have been as inclusive or clear as possible.

SOLUTION: I found various hints in HP C++ User's Guide for OpenVMS Systems (June 2006). It took a lot of reading, and re-reading to isolate issues. Section 7.6.3 Upgrading from the Class Library String Package code was the most help.

I also used & searched the HP C++ Version 7.3 Release notes. I downloaded all the above in pdf for easier searching.

I now have resolved the unresolved symbol(s) and have a working executable.

Re: C++ LINK Issue

Vince M. Kostoff — Mon, 21 Apr 2008 17:33:26 GMT

I resolved the unresolved symbols.

Re: C++ LINK Issue

Steven Schweda — Mon, 21 Apr 2008 19:47:52 GMT

That description of the solution(s) was about
as valuable as the original description of
the problem.

Re: C++ LINK Issue

Vince M. Kostoff — Tue, 22 Apr 2008 12:08:28 GMT

Two things:
1. applying extern "C" around certain functions.

2. The use of string changes from the 5.3 code, to the 7.3 compiler. That is why I highlighted the section: HP C++ User's Guide for OpenVMS Systems (June 2006). Section 7.6.3 Upgrading from the Class Library String Package code was the most help.

All the details for addressing the string changes are contained there.