Setting Up
I like to create a folder to contain the MySQL source code file and build folder. This way, I can later uninstall MySQL easily, as well as download and compile new versions, all in one place.
For these examples, we’ll create a folder called src in our home folder, and change directories into that folder. It will be our workspace for everything we do here:
You’ll download and compile everything in this new folder.
Download, Extract, Etc.
Now we’re ready to start the real work. Just type (or cut-n-paste) each one of the following lines into Terminal, one by one. When one line finishes (some will take a while and dump a lot of information to the screen), enter the next one.
This will first download and then expand the MySQL source code distribution:
You then need to configure MySQL:
When that process completes, you can initiate the actual compilation process:
This part can take a while. Now is a good time to go and get yourself a tasty beverage.
The last part of the build process is where MySQL actually gets installed. You’ll be prompted for your password here, because this is where files actually get written to their actual locations:
Next, we need to setup the initial databases and privileges. You may be prompted for your password again:
That’s it, MySQL is installed. But you’re not done yet.
Auto-Starting MySQL
Now that the install is done, you need to have MySQL auto-start every time you start or reboot your Mac. The easiest way to do this is using launchd.
I’ve prepared a launchd plist file that will manage MySQL, starting it at boot and stopping it cleanly at shutdown. Create a file named com.mysql.mysqld.plist using the text-editor of your choice, and save it to your Desktop. Enter the following text into the file:
Now we need to move the file into place and set the permissions on it. You may be prompted for your password again:
With the file in place, the last step is to tell launchd to load and startup MySQL. You may be prompted for your password again:
If things go well, you won’t see anything special happen, but MySQL will have started up. You can verify this, again back in Terminal:
This will initiate MySQL’s command-line monitor. If everything went well, you should see something like this:
If you see that, that’s it, you’re done! Type exit to quit the MySQL monitor.
If you see something else, verify that your paths are set correctly and try the command again. If things still don’t work, it’s likely that something didn’t work and the compile didn’t finish. Try going through the steps once more and see if you can catch any error messages.
Starting and Stopping MySQL Manually
If you ever want to stop MySQL manually, use this command in Terminal, entering you password when prompted:
sudo launchctl unload -w /Library/LaunchDaemons/com.mysql.mysqld.plist
To start it manually, use this command in Terminal, entering you password when prompted:
sudo launchctl load -w /Library/LaunchDaemons/com.mysql.mysqld.plist
A Note about Security
The easiest way to secure your MySQL installation without affecting the way you (or your applications) will need to communicate with it is to limit anything but local connections to your MySQL server. In other words, only you and the apps you run on your own Mac will be able to connect. You won’t need to enter passwords when interacting with MySQL locally, and won’t need to tweak the default database.yml files that Rails creates, for example.
We can limit access by creating (or editing) the /etc/my.cnf file. If you have TextMate installed, you can enter the following command to create (or edit) the file:
If you use BBEdit, you’d use this command:
The handy bit about using TextMate (or BBEdit) for this task is that it will handle authentication and setting permissions for you.
Enter the following text into the file save it and close it, authenticating as needed:
Thanks to my friend Mike Clark for this tip.
If limiting access isn’t enough for you, you can read about setting a root access password for MySQL in this article.
Baking-In the MySQL Bindings
You can gain some bigtime Rails-to-MySQL speed improvements by building the MySQL C bindings for Ruby.
If you have an Intel Mac, just run the following command (entering your password when prompted):
sudo env ARCHFLAGS="-arch i386" gem install mysql -- --with-mysql-config=/usr/local/mysql/bin/mysql_config
If you have a PPC Mac (I hear some still exist), you’d enter:
sudo env ARCHFLAGS="-arch ppc" gem install mysql -- --with-mysql-config=/usr/local/mysql/bin/mysql_config
You’ll see a prompt asking you which gem to install:
Select which gem to install for your platform (universal-darwin9.0)
1. mysql 2.7.3 (mswin32)
2. mysql 2.7.1 (mswin32)
3. mysql 2.7 (ruby)
4. mysql 2.6 (ruby)
5. Skip this gem
6. Cancel installation
Pick the option closest to the top that ends in “(ruby)”. In the example above, we’d want to select option 3.
Uninstalling MySQL
In case you one day decide that you’d like to remove MySQL, it’s easy to do when building from source:
FAQ :
我安装成功调用:mysqld_safe启动时,报以下错误:
090312 15:57:14 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/webserver/mysql/var/ is case insensitive 090312 15:57:14 [ERROR] /usr/local/webserver/mysql/libexec/mysqld: unknown option '--skip-federated' 090312 15:57:14 [ERROR] Aborting
于是,我找到my.cnf, 注释了--skip-federated,就一切ok了。
#--skip-federated