Bug #28544 Incorrect shared library install name

Description:
Installing MySQL 5.0.41 for 10.4 on OS X places the shared libraries (such as libmysqlclient.15.0.0.dylib ) in /usr/local/mysql/lib .  However, running otool -D on these libraries reveals that their install path is set to /usr/local/mysql/lib/mysql .  This causes an error when trying to configure php5 with pear enabled and I saw some posts around the internet suggesting other bugs (ruby mysql gem).  

See below for quick and dirty fix.

How to repeat:
Install the 5.0.41 mysql package on OS X 10.4.9 (probably on any 10.4).  My install was actually an upgrade so this might be necessary but I doubt it.

Suggested fix:
A quick fix can be had by executing "sudo ln -s /usr/local/mysql/lib/mysql /usr/local/mysql/lib".  Likely a more robust fix would be to use install_name_tool -id to change the library install location but I'm not sure if that is correct and I didn't want to mess with it.  Looking at apple docs it appears that one has to set this information after you build the library with the install_name_tool and can't count on the build process to set it for you but I could be wrong.

The correct solution is to have the package distributed with correct install locations in the libraries.

Thank you for the report.

Verified as described.

same goes for include files. Used to be under /usr/local/mysql/include/mysql and are now on /usr/local/mysql/include.

Possible name conflict can evolve. For example I used:

#include <mysql/errmsg.h>

with the new "stripped mysql subdir" way of doing things, this has to be

#include <errmsg.h>

which might easily clash with current or future system headers with the same name.

Problem still exists with the 5.0.45 release on OS X 10.4.10.  Reverting back to 5.0.37 until this gets fixed.

Will be in 4.1.24, 5.0.48 and 5.1.21

Made the install path "/usr/local/mysql/lib" and
the path compiled into the shared libraries
match.

Noted in 4.1.24, 5.0.48, 5.1.21 changelogs.

On Mac OS X, shared-library installation pathnames were incorrect.

Bug #30160 was marked as duplicate of this one.

Bug #30220 was marked as a duplcate of this one.

Bug #31448 was marked as duplicate of this one.

The problem still exists in the 5.1.22 build, which was the test platform I used when reporting #31448.

Opening; bug still exists in 5.1.22.

I can not repeat the problem using mysql-5.1.22-rc-osx10.4-i686.tar.gz too:

$otool -D lib/libmysqlclient.16.0.0.dylib
lib/libmysqlclient.16.0.0.dylib:
/usr/local/mysql/lib/libmysqlclient.16.dylib

Confirmed fixed in the 5.1.22 and 5.0.50 releases.