Larry Rosenman wrote:
-- Start of PGP signed section.
[moved to -patches because of the patch]
--On Friday, March 19, 2004 08:01:53 -0500 Bruce Momjian
[EMAIL PROTECTED] wrote:
Larry Rosenman wrote:
I thought that once you include libpthread in libpq, that you don't
have to
--On Friday, March 19, 2004 09:18:03 -0600 Larry Rosenman [EMAIL PROTECTED]
wrote:
--On Friday, March 19, 2004 10:15:56 -0500 Bruce Momjian
[EMAIL PROTECTED] wrote:
[moved to -patches because of the patch]
--On Friday, March 19, 2004 08:01:53 -0500 Bruce Momjian
[EMAIL PROTECTED] wrote:
Larry Rosenman [EMAIL PROTECTED] writes:
In other words, the entire application either is or is not linked with
threads; it's not a property of an individual library.
SO, IF we are using the threads flags, we need to use them on ALL=20
libpq-using programs, ours or the users.
Yeek. This is
Bruce Momjian wrote:
Tom Lane wrote:
Larry Rosenman [EMAIL PROTECTED] writes:
In other words, the entire application either is or is not linked with
threads; it's not a property of an individual library.
SO, IF we are using the threads flags, we need to use them on ALL=20
Larry Rosenman wrote:
Yes, his patch ended up adding this to THREAD_LIBS, but
template/unixware has:
For gcc:
THREAD_CPPFLAGS=-pthread
and for non-gcc:
THREAD_CPPFLAGS=-K pthread
Larry, are these wrong?
Nope, those work, and should be passed to any libpq-using
On Fri, 19 Mar 2004, Bruce Momjian wrote:
Larry Rosenman wrote:
Yes, his patch ended up adding this to THREAD_LIBS, but
template/unixware has:
For gcc:
THREAD_CPPFLAGS=-pthread
and for non-gcc:
THREAD_CPPFLAGS=-K pthread
Larry, are these wrong?
Nope,
