[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: back-perl and password/user synchronization

Hi,

I'm working with CVS now, and things look worse :)

According to my understanding of perlembed, dSP C macro expects a 'PerlInterpreter' pointer called 'my_perl' to have been defined. But in ldap/servers/slapd/back-perl/perl_back.h the perl interpreter defined is...
extern PerlInterpreter *perl_interpreter;

I'm currently trying to build add.c and the build is failing with 'my_perl' not found. This is because dSP macro expands to an expression that accesses my_perl structure.

How do you access the perl interpreter in ldap/servers/slapd/back-perl/add.c ? The perl_interpreter pointer is never used as far as I can see.

Also should I define a my_perl structure? eg...
PerlInterpreter *my_perl = perl_interpreter;

Thanks,
--Kervin

Howard Chu wrote: 
Sounds to me like you're trying to mix the 2.1 back-perl with the 2.0 main
slapd code. Won't work.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support


-----Original Message-----
From: Kervin Pierre [mailto:kpierre@fit.edu]
Sent: Wednesday, March 13, 2002 9:25 PM
To: Howard Chu
Cc: lukeh@PADL.COM; openldap-devel@OpenLDAP.org
Subject: Re: back-perl and password/user synchronization



Hi,

I've been working to get 2.0.23+back-perl to compile on the Win32/MSVC++
build with Win32 Perl from ActiveState.

Question about servers/slapd/back-perl/external.h ...

...
extern BI_db_config	perl_back_db_config;
extern BI_op_bind	perl_back_bind;
extern BI_op_search	perl_back_search;
...

These are 3 lines I copied at random from extern.h.  The compiler
complains about every 'extern' declaration in external.h, and frankly, I
can't say I blame it.

Can anyone explain what these lines are doing.

I'm assuming that if it's a prototype for an external function it would
be in the form...

extern return_type function_name( function_args );

but theses are not in that form.  back-ldbm uses the extern prototype
form and does compile, eg...

extern int ldbm_back_db_init LDAP_P (( BackendDB *bd ));
extern int ldbm_back_db_open LDAP_P (( BackendDB *bd ));

Can anyone shed some light on this for me please?  Is this a GCC vs.
MSVC++ thing?

--Kervin


Howard Chu wrote:

Yes, in the time between since I wrote that response and now, I 

have updated

the back-perl code so that it compiles. I also fixed the 

compare operation,

but
I haven't tested it beyond that.

 -- Howard Chu
 Chief Architect, Symas Corp.       Director, Highland Sun
 http://www.symas.com               http://highlandsun.com/hyc
 Symas: Premier OpenSource Development and Support



-----Original Message-----
From: Luke Howard [mailto:lukeh@PADL.COM]
Sent: Wednesday, March 13, 2002 1:25 AM
To: hyc@highlandsun.com
Cc: kpierre@fit.edu; openldap-software@OpenLDAP.org
Subject: RE: back-perl and password/user synchronization





I don't think back-perl has even been supported on Unix for a couple of
years


back-perl built fine on Solaris 2.8 with 2.1.0 alpha, so I think
it is reasonably good shape.

regards,

-- Luke

--
Luke Howard | lukehoward.com
PADL Software | www.padl.com






--
http://linuxquestions.org/ - Ask linux questions, give linux help.







--
http://linuxquestions.org/ - Ask linux questions, give linux help.