[Date Prev][Date Next]
Re: openLdap ucdata error
First: thanks for some great help. It works perfectly. I wonder when
this separate project (unicode) was linked into openldap.
Anyway...while I'm at it I might just make a HOWTO list for W2K for the
build/installation process of the new release of openLdap (2.1.22 in my
case...this is the last stable code and I like things to be stable ;-)
), including how to link you own backend into the project. Anyone
interested in putting such a HOWTO list on the openLdap site or anywhere
else to help other Windows developers?
Howard Chu wrote:
Please remember to mention the operating system you're using when you post a
question. Since you mention the word "project" and the fivesight web site
I'll guess you're using WindowsNT and the MSVC build environment. MSVC is not
actively supported; a lot of the project files are out of date, but it does
work in general.
There is a "ucgendat" program that is compiled as part of the build. This
program must be run with the UnicodeData.txt file as input, to generate the
ucdata tables. The MSVC projects don't do this for you automatically. To
invoke it, run it from a command shell:
\path\to\ucgendat UnicodeData.txt -x CompositionExclusions.txt
copy the resulting *.dat files to a directory that slapd can find them. Make
sure you have the directory set in slapd.conf:
Also note that your Cyrus SASL and Berkeley DB versions are extremely old.
Cyrus SASL 1.5 is too broken to be usable. BDB 4.0 has a couple of resource
leaks as well. You'd do well to upgrade to current revisions of each and
rebuild the OpenLDAP code. It may also be a good idea to get 2.1.23 which was
just released. I suppose since you're using MySQL it's not so critical on the
database side, but there are other bugfixes in there worth having.
-- Howard Chu
Chief Architect, Symas Corp. Director, Highland Sun
Symas: Premier OpenSource Development and Support
Envilogg Datateknik AB