Several people have notified me of the problem they discovered when checking the version that is installed after they manually compiled MySQL from source after the binary install. The mysqld located in ‘/usr/local/mysql/bin‘ directory keeps reflecting the original installed version and not the latest source compiled version.

It took me a while to find out what was wrong here but I solved it. It is my mistake as I did not discover this earlier. The mysqld program when compiling from source is located in ‘/usr/local/mysql/libexec‘ and is properly referenced is you use the ‘mysqld_safe‘ program to start it up. The mysqld binary in ‘/usr/local/mysql/bin‘ is a left-over of the binary install procedure and is no longer used or referenced. This also means that my startup script was incorrect.

As a consequence I’ve changed the startup plist file. Please do the same by first changing the plist file and then do:

sudo launchctl unload /System/Library/LaunchDaemons/com.diymacserver.mysql.plist
sudo launchctl load /System/Library/LaunchDaemons/com.diymacserver.mysql.plist

Then the newer version should be running. You can check this by using the command:

mysqladmin version

Thanks to the vigilant users and my apologies to the others.

For everyone who has upgraded to a 5.1.x version. This is mostly a bug fix release and it is up to you if you want to upgrade. There are no apparent security issues solved in this release.

Check all the fixes and changes that are listed on the release notes to see what issues are resolved and if you are affected.

I’ve compiled this version and did some simple tests on my test servers and it worked without any problems.

Read the documentation on how to ugrade MySQL.

For everyone who has upgraded to a 5.1.x version. This is mostly a bug fix release and it is up to you if you want to upgrade. There are no apparent security issues solved in this release.

Check all the fixes and changes that are listed on the release notes to see what issues are resolved and if you are affected. Most of them are concerning replication.

I’ve compiled this version and did some simple tests on my test servers and it worked without any problems.

Read the documentation on how to ugrade MySQL.

MySQL released new versions of the 5.0.x community version of their database server. There were no security issue releated to this release so if you are not affected I would not advise you to upgrade. I’ve upgraded all my servers without any issue following the normal upgrade path as documented.

Read more about the specifics for this release here: Changes in MySQL 5.0.89

MySQL released new versions of the 5.1.x and 5.0.x community versions of their database server. There is a security issue releated to them so if you are affected I would advise you to upgrade. I’ve upgraded all my servers without any issue following the normal upgrade path as documented.

Read more about the specifics for each release here:

• Changes in MySQL 5.1.41
• Changes in MySQL 5.0.88

MySQL released new versions of the 5.1.x and 5.0.x community version of the database server. As far as I could tell they are bugfix releases and there is no security issue releated to them. I’ve upgraded all my servers without any issue following the normal upgrade path as documented.

Read more about the specifics for each release here:

• Changes in MySQL 5.1.40
• Changes in MySQL 5.0.87

For everyone who has not updated to a 5.1.x version. This is a bug fix release and it is up to you if you want to upgrade. If you don’t have any current issues you don’t need to upgrade.

Check all the fixes that are listed on the release notes to see what issues are resolved and if you are affected.

I’ve compiled this version and did some simple tests on Leopard and Tiger and both can be compiled and installed using the instructions in the documentation set without problems.

Read the documentation on how to ugrade MySQL.

For everyone who has upgraded to a 5.1.x version. This is again a bug fix release like 5.1.39 and it is up to you if you want to upgrade. There are no apparent security issues solved in this release. This is a very quick release after 5.1.38.

Check all the fixes and changes that are listed on the release notes to see what issues are resolved and if you are affected. Most of them are concerning replication.

I’ve compiled this version and did some simple tests on my test servers and it worked without any problems.

Read the documentation on how to ugrade MySQL.

Here is a quick update on getting Apache, PHP and MySQL installations working again after the Snow Leopard upgrade.

For Apache I did a recompile and install because the config was completely lost (and I had no backup!) and this was the quickest way for me. The normal 64 bit Leopard instructions did the job for now, will look later at possible enhancements.

MySQL I could just startup with the System Preferences MySQL panel. Will do a recompile later today and will update this post with the findings. This as MySQL is updated to 5.1.38

PHP gave the most issues, but a comment from Nico helped out. This problem is valid for 5.2.9 and 5.3.0 but it should be solved in 5.3.1 as the bug was listed as solved in 5.3.1.dev

To solve the problem, follow the normal instructions on this site but after the configure statement you need to edit the Makefile which is created by ./configure

You need to add ‘-lresolv‘ at the end of the line which starts with ‘EXTRA_LIBS‘ like:

EXTRA_LIBS = -lmysqlclient -lssl -lcrypto -lz -lssl -lcrypto -lm -lxml2 -lz -licucore -lm -lxml2 -lz -licucore -lm -lmysqlclient -lz -lm -lmysqlclient -lz -lm -lxml2 -lz -licucore -lm -lxml2 -lz -licucore -lm -lxml2 -lz -licucore -lm -lxml2 -lz -licucore -lm -lresolv

As noted earlier, I will keep updating this blogpost till most issues are resolved or properly documented elsewhere on the site.

Update 1: MySQL compiled without a problem using the 64 bits Leopard instructions.

Update 2: Finished some of the PHP documentation on Snow Leopard:

• Compiling PHP in 64 bits mode on Snow Leopard
• Adding the GD module to PHP on Snow Leopard
• Adding the mcrypt module to PHP on Snow Leopard

Update 3: Added Apache install instructions:

• Compiling Apache in 64 bits mode on Snow Leopard

Update 4: Made a new page with all related Snow Leopard instructions. MAMP stack documented, mailserver will follow!

Last update: Mailserver instructions.

Recently I got some remarks from a user who asked why he was not able to compile 64 bits on the PowerPC platform. My notes and instructions did not mention this and I must confess that I had forgotten this as I could not see a PowerMac or iMac G5 as your basic mailserver.

But I’m wrong, as my basic goal was to provide you with a complete mailserver solution, I have to acknowledge that the most polular pages are on installing Apache, PHP and third MySQL. The popularity of the mailserver instructions comes way lower then these three subjects.

So therefore I’ve updated all the 64 bit instructions with how to compile on a 64 bit PowerPC platform. You have to forgive me for not being able to test this (no G5 at my place!) I’m using the input of someone else who told me this. It was a very simple change as you only need to change the ‘x86_64‘ bit into ‘ppc64‘ and that’s it.

If someone else could verify that this works it would be grand!