Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!seismo!rlgvax!hadron!dkp
From: dkp@hadron.UUCP (David K. Purks)
Newsgroups: net.micro,net.micro.pc
Subject: Info needed on Microsoft C Version 3.0
Message-ID: <445@hadron.UUCP>
Date: Sun, 22-Jun-86 09:10:03 EDT
Article-I.D.: hadron.445
Posted: Sun Jun 22 09:10:03 1986
Date-Received: Tue, 24-Jun-86 05:10:49 EDT
Organization: Hadron, Inc., Fairfax, VA
Lines: 22
Xref: linus net.micro:13517 net.micro.pc:8416

I recently purchased a copy of Version 3.0 of the Microsoft compiler (which
includes Version 3.4 of LINK) and have run into a very strange problem.  I
can't make LINK find external subroutines in modules or libraries which were
not compiled with this compiler.  Specifically, I have the GREENLEAF C
function library and WINDOWS (public domain version).  When I reference
functions contained in either of these libraries, LINK is very happy to
inform me that they are unresolved externals.  I have concluded that it is
NOT the linker's fault (I've relinked modules compiled with the old compiler
with the new LINK and everything's fine).  I have tried the -u and -Zl
switches on the compiler to prevent it from putting default library names
in the .OBJ header.  I have also tried extracting the object modules from
the libraries and linking these directly as well as building new libraries.
I do not have the source for these routines.

At this point, I've run out of ideas.  Suggestions (even "give up", if
appropriate) would be greatly appreciated.  If it's not possible to do,
I would just like to know why.  Please e-mail suggestions and information
directly to me and I will post a summary.

Thanks in advance.
Dave Purks
..!seismo!hadron!dkp