I have googled and browsed your mailing list archives for instructions on how to build OpenLDAP for Windows but haven’t found any up-to-date information on it. Is such a thing still supported? I found out that at least Visual Studio workspace files were dropped away some years and versions ago. I would need an OpenLDAP lib that can be linked by Visual Studio 2013 (and probably by later VS versions in the future).


I have Windows 8.1, Cygwin 1.7.35(0.287/5/3) and MinGW. I have tried to do according to this: http://www.openldap.org/faq/data/cache/897.html but ran into issues already in the ./configure phase (btw, it says “WARNING: unrecognized options: --disable-slurpd”). The final error in running that is this: configure: error: select() required.


I’m not familiar with Unixes but Google told me that select() is a native Unix command. Is that correct and if so, what should I do with a Windows machine to handle that? Or should I do the whole building task according to some completely different instructions? I need only the client side of OpenLDAP.


Thanks for any help in advance!


Ps. Just in case it matters, this is the corresponding part extracted from my config.log:


| /* Override any GCC internal prototype to avoid an error.

|    Use char because int might match the return type of a GCC

|    builtin and then its argument prototype would still apply.  */

| #ifdef __cplusplus

| extern "C"

| #endif

| char select ();

| /* The GNU C library defines this for functions which it implements

|     to always fail with ENOSYS.  Some functions are actually named

|     something starting with __ and the normal name is an alias.  */

| #if defined __stub_select || defined __stub___select

| choke me

| #endif


| int

| main ()

| {

| return select ();

|   ;

|   return 0;

| }

configure:14150: result: no

configure:14154: error: select() required.


Learn why you should attend BroadSoft Connections 2015

This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient and have received this email in error, please notify BroadSoft, Inc. immediately by replying to this message, and destroy all copies of this message, along with any attachment, prior to reading, distributing or copying it.