Re: (ITS#5672) Build of back-ndb fails - back-ndb.h:26:22: error: NdbApi.hpp: No such file or directory

[ando@sys-net.it]

hyc@symas.com wrote:
> hyc@symas.com wrote:
>> ando@sys-net.it wrote:
>>> michael@stroeder.com wrote:
>>>> Full_Name: Michael Ströder
>>>> Version: HEAD
>>>> OS: Linux
>>>> URL: ftp://ftp.openldap.org/incoming/
>>>> Submission from: (NULL) (84.163.97.73)
>>>> I think this says it all:
>>>>
>>>> back-ndb.h:26:22: error: NdbApi.hpp: No such file or directory
>>>>
>>>> I could provide the complete build output if needed.
> 
>> As such, this section Works As Designed. ITS will be closed...

Well, the reliability of expecting things to be where people document 
them is the reason autotools were created in the first place... 
however, I'm having other problems right now: NdbInterpretedCode.hpp 
isn't included, so all occurrences of NdbInterpretedCode cause an error; 
but when I explicitly include that header, it requires some other header 
that is not available...  Apparently, I'm using the wrong version, but 
this seems to indicate that the whole Ndb API needs to stabilize.

> 
> Reconsidering... I guess we could add checks for the presence of the required 
> header files and libraries. I'm reluctant to do a full AC_CHECK_HEADER here 
> because that will only succeed if we enable C++ in the configure script, and 
> right now the extra overhead of enabling C++ in libtool doesn't seem worth it. 
> As such, we could just do an AC_PREPROC_IFELSE here.
> 
> (Obviously the back-ndb Makefile requires C++, and it's currently a hack that 
> assumes g++. Frankly I'm revolted at the use of C++ here, but NDB doesn't 
> offer a pure C alternative. I'm stromgly opposed to incurring the overhead of 
> C++ support across the rest of the source tree just for this backend.)

:)

p.


Ing. Pierangelo Masarati
OpenLDAP Core Team

SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
-----------------------------------
Office:  +39 02 23998309
Mobile:  +39 333 4963172
Fax:     +39 0382 476497
Email:   ando@sys-net.it
-----------------------------------