Bug 400631 - cannot compile wine with openldap-2.4
Summary: cannot compile wine with openldap-2.4
Alias: None
Product: Fedora
Classification: Fedora
Component: wine
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: 415331
TreeView+ depends on / blocked
Reported: 2007-11-27 09:11 UTC by Jan Safranek
Modified: 2008-01-03 23:22 UTC (History)
0 users

Fixed In Version: wine-0.9.52-2.fc9
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-01-03 23:22:25 UTC

Attachments (Terms of Use)

Description Jan Safranek 2007-11-27 09:11:35 UTC
Description of problem:

I am preparing rebase of openldap from 2.3 to 2.4 in rawhide. I tried to
recompile all components depending on openldap with new openldap-devel-2.4.
OpenLDAP upstream did not provide any log of API changes or porting guide, so I
assumed the API is the same, but unfortunately wine is the the only component,
which has problems. Compilation results in following errors:

parse.o: In function `ldap_parse_vlv_controlW':
wine-0.9.48-fe/dlls/wldap32/parse.c:420: undefined reference to
wine-0.9.48-fe/dlls/wldap32/parse.c:420: undefined reference to
parse.o: In function `ldap_parse_sort_controlW':
wine-0.9.48-fe/dlls/wldap32/parse.c:339: undefined reference to

These two functions were renamed to 'ldap_parse_vlvresponse_control' and
'ldap_parse_sortresponse_control'. You can distinguish between new and old ldap
headers by checking LDAP_API_FEATURE_SERVER_SIDE_SORT and
LDAP_API_FEATURE_VIRTUAL_LIST_VIEW (see old and new ldap.h).

I'd like to ask you to prepare wine for new openldap-2.4, which you can find in
CVS or as yum repo at
http://people.redhat.com/jsafrane/openldap-2.4-preview/$arch. I want to release
new openldap to rawhide as soon as possible and I want to be sure that everybody
recompiles their packages with openldap-devel, so I can delete compat-openldap.
Please let me know when you are ready.

Comment 1 Andreas Bierfert 2008-01-03 23:22:25 UTC
Wine does check for it in the current release :).

Note You need to log in before you can comment on or make changes to this bug.