Description:
When running mysql-test-run, you cannot specify the location of the binaries or the
libraries that are selected for the test. 

This means that you cannot (easily) test with different versions of client and mysqld
tools, or select for 32-bit or 64-bit binaries/libraries during testing. 

How to repeat:
Run mysql-test-run.

The client binaries and client libraries are loaded from basedir/bin and basedir/lib

basedir is identified as the parent of mtr

Suggested fix:
It would be nice to have two additional options: 

--client-bin-dir
--client-lib-dir

To specify the explicit location of the client binaries and library directories during mtr
execution. These should override any 'implied' setting.

Thank you for the bug report.

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/43310

ChangeSet@1.2580, 2008-03-03 12:47:05+01:00, msvensson@pilot.mysql.com +1 -0
  Bug#34995 mysql-test-run doesn't allow client lib/binary selection

The patch would do the trick and allow to use installed binaries and or libs from specific
directories.

Pushed into 5.0.66  (revid:kgeorge@mysql.com-20080617084217-1u9yw41mpntg7hqk) (pib:2)
(Retry automatic marking, to ensure nothing is missed. cm01)

Pushed into 5.1.27  (revid:joerg@mysql.com-20080626161101-h5hsaluwtf05xdr2) (version
source revid:joerg@mysql.com-20080626161101-h5hsaluwtf05xdr2) (pib:3)

Noted in 5.0.66, 5.1.27 changelogs

mysql-test-run.pl now supports --client-bindir and --client-libdir
options for specifying the directory where client binaries and
libraries are located.

Setting report to NDI pending push into 6.0.x.

Fells like this must be in 6.0 now

Noted in 6.0.10 changelog.