Changes between Version 72 and Version 73 of Mac OS X build instructions

Timestamp:

Sep 8, 2011 12:38:59 PM (13 years ago)

Author:

Christian Pötzsch

Comment:

rpath

Mac OS X build instructions

@@ -113 +113 @@
 }}}
 Another requirement of hardening is that every path component of the parent directory of `VirtualBox.app/` is owned by `root` and not `world` writable. Make sure this is the case.
+=== Relative vs. absolute paths in the used libraries ===
+If you see something like the following error when starting !VirtualBox you need to change the used libraries to use absolute paths.
+{{{
+VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/Applications/VirtualBox.app/Contents/MacOS/VirtualBox.dylib",) failed: \
+ dlopen(/Applications/VirtualBox.app/Contents/MacOS/VirtualBox.dylib, 10): Library not loaded: QtCore.framework/Versions/4/QtCore
+  Referenced from: /Applications/VirtualBox.app/Contents/MacOS/VirtualBox.dylib
+  Reason: unsafe use of relative rpath QtCore.framework/Versions/4/QtCore in /Applications/VirtualBox.app/Contents/MacOS/VirtualBox.dylib with restricted binary
+}}}
+On Mac OS X it isn't allowed to use libraries with relative paths for referencing to other libraries when the executable is setuid. You can display all linked libraries by the following command:
+{{{
+otool -L /Applications/VirtualBox.app/Contents/MacOS/VirtualBox.dylib
+}}}
+Next, assuming Qt is installed in /Applications/VirtualBox.app/Contents/Frameworks/, you can change the path by using this:
+{{{
+install_name_tool -id /Applications/VirtualBox.app/Contents/Frameworks/QtGui.framework/Versions/4/QtGui /Applications/VirtualBox.app/Contents/Frameworks/QtGui.framework/Versions/4/QtGui
+install_name_tool -change @executable_path/../Frameworks/QtCore.framework/Versions/4/QtCore /Applications/VirtualBox.app/Contents/Frameworks/QtCore.framework/Versions/4/QtCore /Applications/VirtualBox.app/Contents/Frameworks/QtGui.framework/Versions/4/QtGui
+}}}
+The first command changes the identifier of the library itself. The second changes references to other libraries. There, the first path is the old referenced path, the second one is the new path and the last path is the file to change (see man install_name_tool). Note, you need to repeat this with every library involved.