From: Tom Lane <tgl@sss.pgh.pa.us>
To: Oleg Bartunov <oleg@sai.msu.su>
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [HACKERS] 6.5 cvs: problem with includes in src/interfaces/libpq++/
Date: Fri, 14 May 1999 17:59:51 -0400
Message-ID: <16288.926719191@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.GSO.3.96.SK.990515003049.24340D-100000@ra>
Oleg Bartunov <oleg@sai.msu.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, oleg@sai.msu.su, pgsql-hackers@postgreSQL.org
Subject: Re: [HACKERS] 6.5 cvs: problem with includes in src/interfaces/libpq++/
In-Reply-To: <16288.926719191@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox