On Aug 25, 2007, at 5:35 AM, ando@sys-net.it wrote:
kurt@OpenLDAP.org wrote:
Entering directory `/Users/kurt/Work/devel/servers/slapd/back-perl' /bin/sh ../../..//libtool --tag=disable-shared --mode=compile cc - g -O2 -I../../../include -I../../../include -I.. -I./.. -I/opt/ local/include -fno-common -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing - pipe -Wdeclaration-after-statement -I/opt/local/include -I/opt/local/lib/perl5/5.8.8/darwin-2level/CORE -I/usr/pkg/ include -I/usr/pkg/include/db45 -c init.c cc -g -O2 -I../../../include -I../../../include -I.. -I./.. -I/opt/local/include -fno-common -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -pipe -Wdeclaration-after-statement -I/opt/ local/include -I/opt/local/lib/perl5/5.8.8/darwin-2level/CORE -I/usr/pkg/include -I/usr/pkg/include/db45 -c init.c -o init.o init.c:90: error: parse error before 'ConfigReply'
ConfigReply is declared in slapd/config.h; could it be another, system-related config.h is present in an earlier include path?
Even though, I see in the above cc command-line -I .. is present...
Personally, I think have -I., -I.., etc. is really bad. This causes #include "config.h" and #include <config.h>
to be equivalent. However, there could be both a local config.h and a config.h somewhere in the system include directory.
I would be better if slapd/config.h was included here by: #include "../config.h"
and -I.. not be added to the include path. It possible -I.. is causing a system header to be eclipsed by the local header. Namely, /opt/local/lib/perl5/5.8.8/darwin-2level/CORE/config.h.
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 Email: pierangelo.masarati@sys-net.it
-
kurt＠OpenLDAP.org