Bug #15017 | Compiling mysql clients fail using 64bit standard binaries for MacOSX 10.4 | ||
---|---|---|---|
Submitted: | 17 Nov 2005 14:02 | Modified: | 6 Mar 2013 9:17 |
Reporter: | Geert Vanderkelen | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Packaging | Severity: | S4 (Feature request) |
Version: | 5.0.15 | OS: | MacOS (MacOSX 10.4 64bit) |
Assigned to: | CPU Architecture: | Any |
[17 Nov 2005 14:02]
Geert Vanderkelen
[22 Nov 2005 19:56]
Jorge del Conde
Verified w/5.0.16bk and 10.4.2
[3 Aug 2006 12:42]
Kent Boortz
Trying to link a 32 bit application with the 64 bit client library part of the 64 bit server package will of course fail. So this is not a bug. But changed this to a "Feature request", as from a user perspective "installing MySQL" should be enough to be able to use the client. And installing two server packages could potentially cause problems with start scripts. There are several possible solutions to this - Separate client packages. Would still require to install a separate new package, but more clear than be forced to install two server packages. - Include both 32 and 64 bit client libraries in both server packages, or at least the 32 bit server package. But as they are installed in "/usr/local/mysql-<version>/lib/..." it is likley still a bit confusing, as the non standard placement requires the user compiling PHP to point to the right client library directory at that location. - Universal binaries. Contains both 32 bit and 64 bit client libraries in the same library file. From a user standpoint the most easy to use solution.
[6 Mar 2013 9:17]
Yngve Svendsen
Rejecting this, since it will realistically never be prioritized highly enough to get resolved.