Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id FAA35016; Sat, 15 May 1999 05:32:41 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id FAA11509; Sat, 15 May 1999 05:12:03 -0400 (EDT) From: Bruce Momjian Message-Id: <199905150912.FAA11509@candle.pha.pa.us> Subject: Re: [HACKERS] 6.5 cvs: problem with includes in src/interfaces/libpq++/ In-Reply-To: <16288.926719191@sss.pgh.pa.us> from Tom Lane at "May 14, 1999 05:59:51 pm" To: Tom Lane Date: Sat, 15 May 1999 05:12:03 -0400 (EDT) CC: Oleg Bartunov , pgsql-hackers@postgreSQL.org, pgsql-interfaces@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > Oleg Bartunov 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 to #include > > #include to #include > > 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. The addition/removal of '.h' has happened before. Some need it, some can't handle it. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026