MySQL and Perl trouble when moving from a PowerPC to an Intel Mac

The Migration Assistant utility in Mac OS X can be a huge time saver when you buy a new Mac and want to move all your stuff from the old machine to the new one.

However, there are a few things to watch out for. One issue I ran into when using Migration Assistant to move from a PowerPC-based Mac to an Intel-based one is that it will copy MySQL and Perl. In my case that meant mysql-standard-4.1.21-apple-darwin8.6.0-powerpc and Perl 5.8.6.

Depending on how you use MySQL and Perl this may or may not be a problem. I’ve been experimenting a bit with Drupal and Joomla, and both appeared to work fine after the move, as did phpMyAdmin. Movable Type, which is Perl-based, did not though – when I tried to log in it gave me an error about DBD::MySQL not being able to connect to MySQL properly.

Both MySQL and Perl are outside my area of expertise, so I didn’t really know where to start looking. But after lots of frustrated searching and asking around I finally managed to get Movable Type working again by updating MySQL and installing some database connection stuff for Perl.

In case I run into the same thing again, and in case somebody else has similar problems, here are some tips (another tip is to make sure you have a fresh backup – but you knew that already):

After all that I was finally able to log into my local install of Movable Type again. Phew.

I’m not quite sure what caused the problem to begin with. I’m guessing either running a PPC version of MySQL on an Intel Mac, something with the older Perl that was copied, or both.

Posted on April 2, 2009 in Mac, Movable Type

Comments are disabled for this post (read why), but if you have spotted an error or have additional info that you think should be in this post, feel free to contact me.