To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=68948
                 Issue #|68948
                 Summary|Wrong install names in synamic shared libraries (e.g. 
                        |berkeleydb)
               Component|porting
                 Version|680
                Platform|Macintosh
                     URL|
              OS/Version|All
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|MacOSX
             Assigned to|pjanik
             Reported by|mox





------- Additional comments from [EMAIL PROTECTED] Fri Aug 25 01:06:01 -0700 
2006 -------
During OOo build process, some of the dylibs get assigned with wrong install
names. This causes runtime failures in some situations.

The affected libaries are at least: libdb-4.2.dylib, libxml2.2.dylib,
libxmlsec1-nss.1.dylib and libxmlsec1.1.dylib

Those libraries report (otool -L <libname>) an install path to /usr/local/lib/,
instead of the wanted: @executable_path/libdb-4.2.dylib

To fix this, we can 1) correct the install names after dylib has been created 
by:
install_name_tool -id @executable_path/libdb-4.2.dylib libdb-4.2.dylib

Or 2) Fix the build process of each library to have something like this:

libtool -dynamic -flat_namespace -install_name
@executable_path/../Frameworks/libbz2.1.0.2.dylib \ -lSystem
-compatibility_version 1.0 -current_version 1.0.2 \ -o libbz2.1.0.2.dylib
-undefined suppress $(OBJS)

The important part being: -install_name @executable_path/<dylibfile>

---------------------------------------------------------------------
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