OpenBSD 3.1 + Apache 2.0.39 + PHP 4.2.2 -> configure problem

Hi all, I've switched to PHP 4.2.2, but all my problems remained the same. [Note: since I'm building for apache 2.0.39, I've patched sapi/apache2filter with php_functions.c from current] Case 1: c-client as a package from OpenBSD 3.1 I need kerberos support for php (which I don't want, I could allow it just to have php working) because my c-client is compiled with kerberos support. If I add --with-kerberos=/usr/lib, I'm stopped with lmysqlclient which doesn't support mysql_error. If I look to config.log (as I'm told to do) I discover that ./configure can't find gssapi_krb5 (which I haven't got, and which I can't install from any OpenBSD package). If I tweak ./configure to skip that test, I'm stopped at the same point because I haven't got k5crypto. Kerberos is just as OpenBSD default installation put it, so it *should* be ok. Case 2: c-client from source (imap-2002rc1.tar.Z or imap-2001a.tar.Z, which I used on Slackware up to last week) I can't build a dynamic library, so php asks me for libc-client.so.* I've looked into imap build directory (since docs say that you just copy files from there), and there's no libc-client.so, I've only found c-client.a (which isn't the same thing, so php doesn't work). As I finish compiling, I'm warned about some library my system hasn't got (and that I should provide) So... Case 3: php configured with --enable-static=most Same as Case 1... Has anybody got an idea? I probably need one of the following things: * an OpenBSD c-client package without kerberos * a way to recompile c-client library from ports without kerberos support * a way to compile a shared c-client library from source distribution (it also should support SSL, but I found this isn't a problem) Again, thank you in advance Michele