On Wed, 3 May 2000, Tom Lane wrote:
> 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.
go for it, I want to do up a quick RC4 with th efixes to the docs that I
did the other day, so let me know when, and I'll do it then ...
