Bug #13158 mysql_config returns erroneous 'libs' under x86_64

Submitted: 13 Sep 2005 22:40 Modified: 14 Apr 2006 14:40
Reporter: Frank Maas (Basic Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:5.0.13 OS:Linux (Linux Fedora 4)
Assigned to: Kent Boortz CPU Architecture:Any

[13 Sep 2005 22:40] Frank Maas
Description:
The mysql_config script that is part of the x86_64 RPM has pkglibdir hard coded set to /usr/lib64/mysql. However this line is immediately followed by

fix_path lib/mysql lib

which resets pkglibdir to {basedir(=/usr)}/lib. As a result the libraries cannot be found by scripts using mysql_config.

How to repeat:
Try installing perl module DBD::mysql

Suggested fix:
The 'fix_path' line should probably be

fix_path lib64/mysql lib/mysql lib64 lib

or even

fix_path lib64/mysql lib64
[13 Sep 2005 22:45] Frank Maas
Severity set to serious, because this bug prevents the implementation of tools, libraries and such that depend on MySQL
[14 Sep 2005 21:31] Jorge del Conde
Verified using FC4 / AMD64
[30 Sep 2005 11:39] Frank Maas
Updated version: problem persists in 5.0.13
[29 Mar 2006 13:00] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/4275
[31 Mar 2006 11:40] Kent Boortz
The script "mysql_config" was changed to search "lib64" and
other special locations, in cases where the hard coded default
path doesn't end in the usual "lib" or "lib/mysql".
[11 Apr 2006 17:33] Mike Hillyer
Version information for the fix?
[11 Apr 2006 21:35] Kent Boortz
Correction will be in 4.1.19, 5.0.20 and 5.1.9 beta
[14 Apr 2006 14:40] Paul DuBois
Noted in 4.1.19, 5.0.20, 5.1.9 changelogs.

<command>mysql_config</command> returned incorrect libraries
on <literal>x86_64</literal> systems. (Bug #13158)

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.041 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.