Howard Chu wrote:
> Joshua Dunbar wrote:
>> After manually adding that symbol to lber.map, make errors our with this:
> 
> Comment out that line and see what else breaks...

Ah never mind. It will complain about struct iovec and writev(). This function 
hasn't been ported
to WIN32. You'll need to work that out or wait for someone else to do it.
>>
>> cc -g -O2 -I../../include -I/c/openldap-2.6.1/servers/slapd 
>> -I/c/openldap-2.6.1/servers/slapd/slapi -I. -I/c/openldap-2.6.1/include      
>>  -c -o logging.o /c/openldap-2.6.1/servers/slapd/logging.c
>> C:/openldap-2.6.1/servers/slapd/logging.c:28:10: fatal error: sys/uio.h: No 
>> such file or directory
>>    28 | #include <sys/uio.h>
>>       |          ^~~~~~~~~~~
>> compilation terminated.
>> make[2]: *** [<builtin>: logging.o] Error 1
>> make[2]: Leaving directory '/home/USAF_Admin/servers/slapd'
>> make[1]: *** [Makefile:299: all-common] Error 1
>> make[1]: Leaving directory '/home/USAF_Admin/servers'
>> make: *** [Makefile:320: all-common] Error 1
>>
>> -----Original Message-----
>> From: Quanah Gibson-Mount <[email protected]> 
>> Sent: Friday, February 18, 2022 3:58 PM
>> To: Joshua Dunbar <[email protected]>; Howard Chu 
>> <[email protected]>; Dr. Ogg <[email protected]>
>> Cc: [email protected]
>> Subject: RE: Error when running make test or slapd after building on windows
>>
>>
>>
>> --On Friday, February 18, 2022 5:39 PM +0000 Joshua Dunbar 
>> <[email protected]> wrote:
>>
>>> It seems to be specific to 2.6.1, I was able to build 2.5.10 without 
>>> seeing that error using MSYS. The tests still fail due to the paths 
>>> not resolving on windows, but I was able to make my own slapd.conf 
>>> file with correct paths and get slapd to start.
>>
>> You have to manually add the symbol to the libraries/liblber/lber.map file 
>> before building.
>>
>> --Quanah


-- 
  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/

Reply via email to