openldap 2.1.22-r1

[SillyPants]

This isn't compiling. I get

Code: Select all

init.c: In function `perl_back_initialize':
init.c:74: warning: passing arg 2 of `perl_parse' from incompatible pointer typeinit.c: In function `perl_back_db_open':
init.c:147: error: `my_perl' undeclared (first use in this function)
init.c:147: error: (Each undeclared identifier is reported only once
init.c:147: error: for each function it appears in.)
init.c: In function `perl_back_xs_init':
init.c:182: error: `my_perl' undeclared (first use in this function)
init.c:182: warning: passing arg 3 of `Perl_newXS' from incompatible pointer type
make[3]: *** [init.lo] Error 1
make[3]: Leaving directory `/var/tmp/portage/openldap-2.1.22-r1/work/openldap-2.1.22/servers/slapd/back-perl'
make[2]: *** [.backend] Error 1
make[2]: Leaving directory `/var/tmp/portage/openldap-2.1.22-r1/work/openldap-2.1.22/servers/slapd'
make[1]: *** [all-common] Error 1
make[1]: Leaving directory `/var/tmp/portage/openldap-2.1.22-r1/work/openldap-2.1.22/servers'
make: *** [all-common] Error 1
 
!!! ERROR: net-nds/openldap-2.1.22-r1 failed.
!!! Function src_compile, Line 100, Exitcode 2
!!! make failed

[474]

Try prefixing your emerge command with:

Code: Select all

USE="-perl"

If this issue seems to be reproducible then you should file a bug.

[POLAX]

The workaround allowed it to compile. I have a funny feeling that this has something to do with compiling perl with the "threads" option

[474]

Well, I never ecountered the problem and the cause isn't immediately apparent to me from that report above (it seems to refer to the perl embedding functions). However, I can say this: threads support should probably be avoided like the plague. I tried it briefly once, and it broke various things.

I don't think there's much to be gained from it, nor is it as cool as it sounds - as far as I know, it's an entirely self-contained threading mechanism so you don't have anything to gain if, say, you're using a NPTL-enabled glibc. I don't know of anything specifically using the implementation either (which, incidentally, is covered nicely here.