Article View: comp.os.os2.programmer
Article #1938CSet/2 Linking Conflict
From: Tim Francis
Date: Wed, 07 Oct 1992 22:10
Date: Wed, 07 Oct 1992 22:10
31 lines
1831 bytes
1831 bytes
In article <92281.101301UD092096@NDSUVM1.BITNET>, Barry Pederson <UD092096@NDSUVM1.BITNET> writes: > >I'm working on a program with the CSet/2 compiler and Workframe/2, and am >having some trouble linking a certain program. > >I'm trying to write a program that uses both the IBM TCP/IP tcpip.dll and >the Lotus VIM developers toolkit vim.dll. I've had good luck with programs >that use one or the other, but the two together don't seem to get along. > >The problem is that to use tcpip.dll, you have to link with the linker's >"Do not ignore case in symbol names" option activated. Otherwise > >at runtime it aborts with sys2070 (can't load the needed segment) and >sys127 (the specified procedure could not be found) > >VIM, on the other hand, seems to require that you DON'T have "Do not ignore >case in symbol names" activated, otherwise the linker complains about >unresolved externals. > >What can a person do in a situation like this? > > Barry > The fact that you can "ignore case in symbol names" for VIM would not be a requirement -- it would just mean that the function names you use could be whatever case you wanted (mixed, presumably). As you require the linker to respect the case (for TCP/IP), simply use the correct case for your VIM functions. What the correct case is, I have no idea. All uppercase, perhaps? -tim
Technical Details
Message-ID:
<19921007.150857.182@almaden.ibm.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!vnet.ibm.comReferences:
<92281.101301UD092096@NDSUVM1.BITNET>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!vnet.ibm.com From: francis@vnet.ibm.com (Tim Francis) Message-ID: <19921007.150857.182@almaden.ibm.com> Date: Wed, 7 Oct 92 18:10:29 EDT Subject: CSet/2 Linking Conflict Newsgroups: comp.os.os2.programmer References: <92281.101301UD092096@NDSUVM1.BITNET> Reply-To: francis@vnet.ibm.com Organization: IBM Canada Lab, WorkFrame/2 development Disclaimer: This posting represents the poster's views, not those of IBM Lines: 31