The woes of Mysql and Leopard.

1 November, 2007 (23:23) | Apple/Mac, PHP and MySQL | By: Rawrb

Wow, how shocking was this. Right now I’m downloading PHP 5 for Leopard.

“But Rawrb, it comes installed with PHP 5!”

Shut up. It does. But it doesn’t have the GD library! WHAT?! Yes, that’s right. It’s NOT ON THERE. Why would you exclude that? WHY?! So here I am. What a pain. Just for those who don’t know, the GD library is an awesome feature that allows you to autothumbnail images on your websites. I use it like crazy.

But no, that php thing is not my beef for today. No, my beef is MySql for Leopard.

Now at first I read that mysql comes pre-installed with Leopard. Incorrect. It’s NOT pre-installed. So yes, I went to download and install it. Ok, cool, it’s installed. I install the MySql Admin utility they offer at Mysql’s website. It shows it as running. Oh, but wait! The mysql.sock file needs an alias created in the /var/mysql or the /tmp directory. What? Okay… sure. I dig around on the net, and I end up created two aliases without even knowing it, seemingly removing the original mysql.sock file. Ugh.

So I attempt to reinstall mysql, but it doesn’t install a new mysql.sock file. Nope. It has a blank my.cnf file that I had to… create? Erase? I don’t remember anymore. Blah.

I’m at my wit’s end by this time. PHP works (no GD unbeknownst to me). Mysql is not working. After several attempts to find a solution, and posting on Apple’s support site, I install the mysql.prefpane thingie that came with the Mysql dmg file downloaded with MySql itself.

Boom, it works! I reboot to make sure, and sure enough – it’s working!

So in the migration to Leopard, somehow they decided to move the mysql.sock location? Why would you do that? Maybe I’m just confused. I’m happy now that I have it working.

Now to reinstall PHP 5. Not something I’m looking forward to. Maybe this time I’ll get mod-rewrite to work on my local machine this time without breaking Apache or something. Fuck.

Rant OVAR!