Skip site navigation (1) Skip section navigation (2)


From: bcsaba(at)balmazujvaros(dot)hu
To: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: BLIBPQ.LIB, BLIBPQDLL.LIB or LIBPQ 7.4 problem
Date: 2004-04-22 07:13:58
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
L J Bayuk <ljb220(at)mindspring(dot)com> wrote:

> Mine would crash whenever a notification message was received (like primary
> key create). The crash is in fprintf(stderr, ...), and the explanation I
> got was that the I/O runtime wasn't initialized properly inside the Borland
> DLL. But then, I was linking my BLIBPQ DLL with a MSVC-compiled program
> (ActiveTcl), so maybe your case is different. The fix was easy: link with
> Borland's "static" version of the runtime "cp32mt.lib" instead of
> "cp32mti.lib".  But again: that was because I was using the BCC-compiled
> DLL with a MSVC-compiled program. Your case may be different, and your
> library name is different (CC3250MT), but look for a static runtime instead
> of an import library runtime and try linking with that.

Thank you!
The same was here after adding cp32mt.lib to my component package and recompiled
the components, the problem solved and it is working fine now.

Csaba Bistey

This message was sent using IMP, the Internet Messaging Program.

In response to

pgsql-interfaces by date

Next:From: brian plummerDate: 2004-04-23 23:58:22
Subject: I hope I'm missing something...
Previous:From: L J BayukDate: 2004-04-21 22:39:16
Subject: Re: BLIBPQ.LIB, BLIBPQDLL.LIB or LIBPQ 7.4 problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group