On Sun, Nov 14, 2004 at 05:40:38PM -0800, Glenn Fleishman wrote:

Actually, no - it depends on the installation type. If you installed the MySQL server and client from the packages supplied at the mysql.com website, then most probably those directories should exist. If, however, your MySQL server and client installation came from your OS's vendor packages - e.g. RPM's found on RedHat install CD's, Debian .deb files, FreeBSD ports/packages or something - then the installation directory may not necessarily be /usr/local/mysql. You might have to look for a mysql_config script - check if there is a /usr/bin/mysql_config, /usr/local/bin/mysql_config, or just do a "whereis mysql_config" or, if that fails, "locate mysql_config". It will tell you best where to find your MySQL installation :)

By the way, the key to the errors you are getting in the DBD::mysql installation is mostly that - the DBD::mysql Makefile.PL cannot find the mysql_config script, which is supposed to tell it where to find the header files and the library. If you can find mysql_config on your system, then the best way to build DBD::mysql would be to add to your PATH variable the directory where mysql_config lives, so Makefile.PL can find it. If you are using a Bourne-like shell (sh, ksh, bash, zsh, ...), and if, say, you find mysql_config in /usr/mysql/bin/mysql_config, then do the following:

PATH="/usr/mysql/bin:$PATH" export PATH

For csh-like shells, that would be:

set path = ( /usr/mysql/bin $path )

After that, re-running 'perl Makefile.PL' for DBD::mysql should work just fine.

[snip other commands]

Of course, that's assuming that 'mysql-distribution-name' refers to an official distribution obtained from the mysql.com download sites :)

G'luck, Peter