Hi Umdurman,

I don't have much that you'll want to hear, sorry ...

Personally I gave up on MacPorts for Perl and for MySQL because I was running into lots of problems like the one you described. Can't recall the details but I know I got so sick of it I switched back to installing MySQL using the native package installer available from MySQL (I most recently used mysql-5.6.26-osx10.9-x86_64.dmg ... latest docs here ).

I then made sure to install my own version of Perl using Perlbrew, leaving the Mac OSX system Perl completely out of it.

This allows me to use CPAN via cpanm and just install Perl modules as normal, including the DBI and DBD::mysql.

One thing I remember I had to do was symlink this dynamic library:

sudo ln -s /usr/local/mysql/lib/libmysqlclient.18.dylib /usr/lib/libmy
+sqlclient.18.dylib
[download]

(and if you are on El Capitan or newer you'll have to disable SIP in order to create the symlink.)

It may be just me, but for > 20 years I've had a much easier time using CPAN than with any of the pre-packaged systems, this is going back to FreeBSD (which of course OS X is based on). I do use MacPorts for certain other packages, because it sure does work well in most cases, but I've just always run into conflicts when it comes to MySQL/Perl/DBD::mysql.

There are other packagers for Mac, including Homebrew, which is very easy to use, and MAMP, which you might like, because it installs Apache with mod_perl as well as MySQL and Perl.

I no longer use Apache/mod_perl, and to be sure I remember that installing that combo manually was sometimes tricky, so I don't know what I'd do if I needed it, but for a long time what has worked best for me on OS X is:

• the native package installer for MySQL
• perlbrew for Perl
• CPAN for Perl modules
• MacPorts for libraries like ImageMagick, Cairo, openssl, libxml2 etc.

Hope this helps (a little) !