MySQL Improperly Configured: Addressing the "unsafe use of relative path" Error
When running Python's manage.py runserver with Django, you may encounter the infamous error:
"ImproperlyConfigured: Error loading MySQLdb module: dlopen([path to _mysql.so], 2): Library not loaded: libmysqlclient.18.dylib Reason: unsafe use of relative rpath libmysqlclient.18.dylib in [_mysql.so] with restricted binary"
Cause:
In macOS El Capitan (10.11), Apple introduced System Integrity Protection, which restricts protected programs like MySQL from calling shared libraries with relative references to other libraries. This is an issue because _mysql.so, a shared library required by MySQLdb, contains a relative reference to libmysqlclient.18.dylib.
Solution:
Until the library is updated, you can force it to use an absolute reference using the install_name_tool utility:
sudo install_name_tool -change libmysqlclient.18.dylib \ /usr/local/mysql/lib/libmysqlclient.18.dylib \ /Library/Python/2.7/site-packages/_mysql.so
Example:
Assuming libmysqlclient.18.dylib is located at /Users/Applications/My_Applications/MySQL/lib/, the command would be:
sudo install_name_tool -change libmysqlclient.18.dylib \ /Users/Applications/My_Applications/MySQL/lib/libmysqlclient.18.dylib \ /Library/Python/2.7/site-packages/_mysql.so
Note:
This solution may not work until you update to a newer version of MySQL that supports macOS El Capitan's security measures.
The above is the detailed content of How to Fix the \'unsafe use of relative rpath libmysqlclient.18.dylib\' Error on macOS El Capitan?. For more information, please follow other related articles on the PHP Chinese website!