Re: How to get development headers and mysql client libraries for DBD::mysql installation

[kcott]

G'day Perl300,

In the first instance, I would check DBD::mysql::INSTALL. This has a lot of information, including "How to get development headers and mysql client libraries".

While I'm very much guessing here, I suspect the source of your problem occurs before make is run. It could be the value of environment variables, the location or content of mysql_config, or something else like that. DBD::mysql::INSTALL discusses these things.

I'd also check your $PATH. A common problem (using cpan as an example) is that `which cpan` returns /system/path/bin/cpan instead of /local/path/bin/cpan.

I'm also a little concerned about seeing pathnames starting with '~/'. At one point you talk about an "application owned directory"; I assume you have your own account; and perhaps, at times, you're operating as the superuser. Does '~/' equal '/home/application/', '/home/perl300/' or '/home/root/'? I'm not saying don't use '~/', I use it myself a lot on the command line; however, there are times when an absolute pathname makes it unequivocally obvious what file(s) you're referencing.

You might also consider using perlbrew. I know many people here use and recommend it (including myself). It's a very easy way of keeping your local and system Perl installations separate. It also allows you to have multiple Perl versions installed locally and to quickly switch from one to another with a single, short command.