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