Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.9.3/8.9.3) with ESMTP id NAA53782
	for <pgsql-hackers@postgreSQL.org>; Wed, 3 May 2000 13:39:47 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id NAA08428;
	Wed, 3 May 2000 13:38:56 -0400 (EDT)
To: frank <f.callaghan@ieee.org>
cc: pgsql-hackers@postgreSQL.org
Subject: Re: 7.0RC2 compile error ! 
In-reply-to: <391053AD.C8706034@ieee.org> 
References: <200005030227.WAA05863@candle.pha.pa.us>
	<390FB047.CD8B8BA5@alumni.caltech.edu>
	<39102A85.473BFC36@ieee.org> <20000503101756.A16305@rice.edu>
	<7839.957368619@sss.pgh.pa.us> <39103FAE.14920C31@ieee.org>
	<8030.957370504@sss.pgh.pa.us> <391053AD.C8706034@ieee.org>
Comments: In-reply-to frank <f.callaghan@ieee.org>
	message dated "Wed, 03 May 2000 12:28:29 -0400"
Date: Wed, 03 May 2000 13:38:56 -0400
Message-ID: <8425.957375536@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200005/172

frank <f.callaghan@ieee.org> writes:
> Yup your dead right, the <string> include failed in the configure.
> Isn't configure supposed to tell the user that something failed ?,
> I have no idea what is an acceptable configuration for this s/w !

> checking for namespace std in C++... yes
> checking for include <string> in C++... no
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Yup, there's our problem.  Your C++ setup is evidently pretty modern,
since it knows what namespace std is.  My guess is that you don't have
the headers for libstdc++ installed.

It would probably be a good idea to add another configure test to see
whether class "string" is actually available, and disable building
libpq++ if not.  (We shouldn't simply kill libpq++ if the "include
<string>" test fails, since older C++ installations may have class
string in <string.h>.  But if we can't find a header that defines class
string at all, then libpq++ is definitely going to fall over.)

Any objections if I sneak in such a configure test?  Should be a
low-risk change.

			regards, tom lane