Mysql_config not found when installing mysqldb python interface

sql

mysql-config

mysql-python

pip-installation

byAlex Kataev·Sep 20, 2024

A fast solution for mysql_config not found error is to install the MySQL development package as per your system:

Debian/Ubuntu:

# Because why not? Let's make the system more dev-friendly!
sudo apt-get install libmysqlclient-dev

Red Hat/CentOS/Fedora:

# More yum for your system!
sudo yum install mysql-devel  # For CentOS/RHEL
sudo dnf install mysql-devel  # For Fedora

And if you're playing hide-and-seek with your mysql_config in a different path or within a virtual environment:

# Here we go, custom configs! Let's get this show on the road!
pip install MySQL-python --install-option='--mysql-config=[your-custom-path-to-mysql_config]'

Replace [your-custom-path-to-mysql_config] with your custom path. And voila, your MySQLdb install issues are ancient history!

Setting things straight: MySQL and Python devil's pact

Initially, your system should be ready with MySQL correctly installed. Verify it with a sanity check:

# Ask MySQL for an autograph
mysql --version

Got a version number? Great! MySQL is on board. If not, Houston we've a problem - the solution, get MySQL server installed first.

For the Python 3.x warriors out there, your suit of armor is python3-dev. It brings along the header files needed to build Python extensions:

sudo apt-get install python3-dev  # Debian/Ubuntu
sudo yum install python3-devel    # CentOS/RHEL

Now, if mysql_config still plays hard to get, add the MySQL bin directory to your path:

# The system's PATH, the high-school reunion for commands
export PATH=$PATH:/usr/local/mysql/bin

And for the stubborn edge cases, creating a symlink for libmysqlclient might be the final straw:

# Link. Not your favorite Zelda character.
sudo ln -s /usr/lib/x86_64-linux-gnu/libmysqlclient_r.so /usr/lib/

When the usual suspects don't line up (Alternative packages and variables)

Sometimes, just sometimes, conventional wisdom might not work. In that case, try using the alternative mysql-connector-c:

# Plan B, activate!
pip install mysql-connector-c

Encounter an SSL related issue or something suspicious with openssl? Reinstall it, no second thoughts:

# A fresh coat of paint for openssl
sudo apt-get install --reinstall openssl

Define the LIBRARY_PATH environment variable to help in locating the correct mysqlclient libraries:

# It's always about location, location, location
export LIBRARY_PATH=/usr/local/mysql/lib/

But if pip gives you nightmares, easy_install is your superhero to fall back on:

# Because easy does it
easy_install mysql-python

Remember to always stay tuned with community updates. You never know when a new shiny solution pops up to help with mysql_config conundrums.

Outcome:

Artist 👩‍💻 -> Tool 🛠️ -> Bucket 🪣 -> Water 🌊 (MySQLdb)


## Troubleshooting like a pro

Not every day is a sunny day. Brace yourself for these obstacles you might face:

### System-specific issues

- Diverse Linux distributions = diverse package names. How to solve the diversity problem:

  ```bash
  # Everyone loves a good search!
  apt-cache search mysql | grep dev  # For Debian/Ubuntu
  yum search all mysql | grep devel  # For CentOS/RHEL

The phantom of virtual environments

When working in virtual environments, mysql_config might be playing hide and seek. Let's smoke it out:
```
# Marco..?
which mysql_config
```
Use the returned path with --install-option during pip installation.

Package maintainers headache

If you're packing your code into a distributable, the dynamic linking of libmysqlclient might get you pulling your hair. Avoid the bald look:
```
# The correct path. No, not the spiritual one.
export LD_RUN_PATH=/path/to/mysql/lib
```
Cross verify the correctness of the path for the target systems.