To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=111316





------- Additional comments from [email protected] Mon May  3 17:36:23 
+0000 2010 -------
In response to your request for more information:

I first installed Via zypper using the Suse repositories and packman. This was,
I believe V.3.0. When this was a problem, I updated using the RPM from you web
site (3.2). Still, there was a problem. I uninstalled using the RPM, than zypper
and since I keep a log when installing Via RPM, I checked all the installation
files and other changes and removed everything. At this point, zypper worked
fine with libldap-2.4 (I moved libldap-2.3 from /usr/local/lib and ran
ldconfig). I than re-installed from your RPM, zypper again was asking for
libldap-2.3. Currently I am using 3.2 and simply put a copy of the older shared
objects in /usr/local/lib. Since LDAP is used by multiple applications, leaving
both on the system should not be a problem. The OpenSUSE forum has not offered
any usable solutions nor a way to change the bindings of Yast/Zypper to use a
specific version of LDAP. Since I'm not familiar with LDAP, I'm not sure how
applications access it from the ldconfig(8) data hash used by the dynamic
linker/loader.

Thanks for the follow up. In the past, I have written kernel code (Bell Labs,
SVID.3 and SVID.4) and will follow this up with tools when I feel the ambition.
Dynamic bindings can be a pain to follow though I have turned on sar to see if
something simple is possible.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to