From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | frank <f(dot)callaghan(at)ieee(dot)org> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: 7.0RC2 compile error ! |
Date: | 2000-05-03 17:38:56 |
Message-ID: | 8425.957375536@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-interfaces |
frank <f(dot)callaghan(at)ieee(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Mitch Vincent | 2000-05-03 17:44:21 | Re: Why Not MySQL? |
Previous Message | Tom Lane | 2000-05-03 17:31:52 | Re: Why Not MySQL? |
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 2000-05-03 18:03:27 | Re: 7.0RC2 compile error ! |
Previous Message | The Hermit Hacker | 2000-05-03 17:08:42 | Re: 7.0RC2 compile error ! |