Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67])
	by hub.org (8.9.3/8.9.3) with ESMTP id XAA78244
	for <pgsql-hackers@postgreSQL.org>; Thu, 4 May 2000 23:56:08 -0400 (EDT)
	(envelope-from pgman@candle.pha.pa.us)
Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id
 XAA08134;
	Thu, 4 May 2000 23:55:52 -0400 (EDT)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200005050355.XAA08134@candle.pha.pa.us>
Subject: Re: 7.0RC2 compile error !
In-Reply-To: <8425.957375536@sss.pgh.pa.us> from Tom Lane at "May 3,
	2000 01:38:56 pm"
To: Tom Lane <tgl@sss.pgh.pa.us>
Date: Thu, 4 May 2000 23:55:52 -0400 (EDT)
CC: frank <f.callaghan@ieee.org>, pgsql-hackers@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL72 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200005/282

> 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
> 

I would like to see one other user with the problem first.


-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  pgman@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