Re: [HACKERS] 6.5 cvs: problem with includes in src/interfaces/libpq++/

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
Cc: pgsql-hackers(at)postgreSQL(dot)org, pgsql-interfaces(at)postgreSQL(dot)org
Subject: Re: [HACKERS] 6.5 cvs: problem with includes in src/interfaces/libpq++/
Date: 1999-05-14 21:59:51
Message-ID: 16288.926719191@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-interfaces

Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> writes:
> To compile postgres using gcc 2.7.2.1 I had to modify 2 files
> src/interfaces/libpq++/pgconnection.cc
> src/interfaces/libpq++/pgenv.h
> Particularly,
> #include <iostream> to #include <iostream.h>
> #include <strstream> to #include <strstream.h>

I am seeing the same thing here with gcc 2.7.2.2. We need to adopt
a considered policy about whether libpq++ will still support gcc 2.7.*,
not just break it without thinking.

I'd vote for still supporting 2.7.*, but I know that the C++ library
shipped with this gcc release is not real up-to-date. It may not be
practical to support both latest-C++-spec compilers and the older
generation; I'm not sure what the issues are.

If the conclusion is "no", then the configure script ought to be
changed to not try to build libpq++ unless up-to-date libraries
are available.

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 1999-05-15 00:54:18 Re: [HACKERS] postgresql bug report (fwd)
Previous Message Tom Lane 1999-05-14 21:51:09 Re: [HACKERS] rules regression test

Browse pgsql-interfaces by date

  From Date Subject
Next Message leif 1999-05-15 08:31:47 [INTERFACES] M and primary keys
Previous Message Alf Lewerken 1999-05-14 21:07:56 libpq++ and arrays?