Re: libpq++ memory problems - Mailing list pgsql-interfaces

From Lamar Owen
Subject Re: libpq++ memory problems
Date
Msg-id 38FF243E.E5C0E87E@wgcr.org
Whole thread Raw
In response to libpq++ memory problems  (Tim Brookes <tim.brookes@mcmail.com>)
Responses libpq++ tracing considered harmful (was Re: libpq++ memory problems)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-interfaces
Tim Brookes wrote:
> 
> Tom
> 
> I did not use configure - I downloaded a set of RPMs for 6.5.3
> I then just changed the program not to require PgEnv and then compiled,linked with
> the libpq++ library.

To answer Tom's question:

> > I wonder if it could be platform- or configuration-specific.  What
> > options did you give to configure?

To which I can answer, if it was my RPMset he downloaded:
CFLAGS="$RPM_OPT_FLAGS" ./configure --prefix=/usr \--enable-hba --enable-locale \--with-perl
--with-mb=SQL_ASCII\--with-tcl--with-tk --with-x \--with-odbc --with-java \--with-python
 

--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11


pgsql-interfaces by date:

Previous
From: Tim Brookes
Date:
Subject: Re: libpq++ memory problems
Next
From: "Ken J. Wright"
Date:
Subject: Re: Inserting NULL with pgaccess