From:	Anthony AT computronix DOT com (Anthony Tuininga)
Subject:	Link Failure with 3rd party Windows DLLs
24 Aug 1997 15:38:57 -0700 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<408173704E9ED011A9DB00009296CA0010D003.cygnus.gnu-win32@alpha.computronix.com>
Mime-Version:	1.0
Original-To:	"'gnu-win32 AT cygnus DOT com'" <gnu-win32 AT cygnus DOT com>
X-Priority:	3
X-Mailer:	Internet Mail Service (5.0.1457.3)
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

I looked at the mailing list archive and noticed that one other person
got this result and had queried the list but I haven't seen a response
to date. Perhaps this information will make it easier to track down the
problem and suggest a solution -- I am a programmer by trade and so do
not necessarily have a problem with making the fix myself. Note that I
am not a compiler/linker programmer, however. :-)

I compiled and linked successfully a C program (one of Oracle's OCI demo
programs) against the OCIW32.LIB (Oracle Call Interface library) which
contains pointers to the OCIW32.DLL and I got the following result when
I tried to run the program:

The procedure entry point  could not be found in the dynamic link
library OCIW32.DLL.

Using nm and the link I noticed that the call points are null in the
library OCIW32.LIB which seems the root cause of the problem (or is this
normal?). Trying nm on the DLL itself simply says "no symbols".

Any pointers at all are appreciated! I really like the GCC/G++ compilers
and have used them extensively over the past five years -- this port to
Windows NT will really make life a lot easier for me!

Anthony

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -