源码编译安装MySQL5.6.12详细过程_MySQL-Mysql Tutorial-php.cn

Home

Database

Mysql Tutorial

源码编译安装MySQL5.6.12详细过程_MySQL

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB

May 31, 2016 am 08:50 AM

1 下载安装包download tar.gz

wget http://download.csdn.net/detail/mchdba/7545037

2 安装cmake软件包

yum install cmake -y

3 create account of mysql

groupadd mysql

useradd -g mysql mysql

autoreconf --force --install

libtoolize --automake --force

automake --force --add-missing

4 complie the sources

数据目录 : /home/data/mysql/data

mysql软件目录 : /usr/local/mysql

mkdir -p /home/data/mysql/data

mkdir -p /usr/local/mysql

tar -xvf mysql-5.6.12.tar.gz

cd mysql-5.6.12

5 预编译

[root@squid-2 mysql-5.6.12]# time cmake . -DCMAKE_INSTALL_PREFIX=/usr/local/mysql -DMYSQL_DATADIR=/home/data/mysql/data -DWITH_INNOBASE_STORAGE_ENGINE=1 -DMYSQL_UNIX_ADDR==/usr/local/mysql/mysql.sock -DMYSQL_USER=mysql -DDEFAULT_CHARSET=utf8 -DDEFAULT_COLLATION=utf8_general_ci

......

-- Check size of wint_t

-- Check size of wint_t - done

-- Could NOT find Curses (missing: CURSES_LIBRARY CURSES_INCLUDE_PATH)

CMake Error at cmake/readline.cmake:85 (MESSAGE):

Curses library not found. Please install appropriate package,

remove CMakeCache.txt and rerun cmake.On Debian/Ubuntu, package name is libncurses5-dev, on Redhat and derivates it is ncurses-devel.

Call Stack (most recent call first):

cmake/readline.cmake:128 (FIND_CURSES)

cmake/readline.cmake:202 (MYSQL_USE_BUNDLED_EDITLINE)

CMakeLists.txt:325 (MYSQL_CHECK_EDITLINE)

-- Configuring incomplete, errors occurred!

real 0m41.872s

user 0m23.508s

sys 0m16.328s

6 yum install make

[root@472322 mysql-5.6.13]#

[解决]

删除txt

[root@squid-2 mysql-5.6.12]# find / -name CMakeCache.txt

/root/mysql/mysql-5.6.12/CMakeCache.txt

安装ncurses-devel

yum -y install ncurses-devel

再报错如下：

-- Performing Test HAVE_PEERCRED

CMake Error at /usr/share/cmake/Modules/CMakeCXXInformation.cmake:17 (GET_FILENAME_COMPONENT):

get_filename_component called with incorrect number of arguments

Call Stack (most recent call first):

CMakeLists.txt:3 (PROJECT)

CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage

CMake Error: Internal CMake error, TryCompile configure of cmake failed

-- Performing Test HAVE_PEERCRED - Failed

-- Library mysqlclient depends on OSLIBS -lpthread;m;rt;dl

-- Googlemock was not found. gtest-based unit tests will be disabled. You can run cmake . -DENABLE_DOWNLOADS=1 to automatically download and build required components from source.

-- If you are inside a firewall, you may need to use an http proxy: export http_proxy=http://foo.bar.com:80

Warning: Bison executable not found in PATH

-- Library mysqlserver depends on OSLIBS -lpthread;m;rt;crypt;dl

-- Configuring incomplete, errors occurred!

real 0m42.841s

user 0m24.527s

sys 0m16.543s

-- Configuring incomplete, errors occurred!

real 0m0.510s

user 0m0.275s

sys 0m0.112s

[root@472322 mysql-5.6.13]#

yum install gcc gcc-c++ -y

yum install -y ncurses-devel.x86_64

yum install -y cmake.x86_64

yum install -y libaio.x86_64

yum install -y bison.x86_64

yum install -y gcc-c++.x86_64

[解决办法]：删除原来的mysql-5.6.12目录，重新解压缩tar.gz包

8 重新执行编译

rm -rf /root/mysql-5.6.12

cd /root/

tar -xvf mysql-5.6.12.tar.gz

cd /root/mysql-5.6.12

time cmake . -DCMAKE_INSTALL_PREFIX=/usr/local/mysql -DMYSQL_DATADIR=/home/data/mysql/data -DWITH_INNOBASE_STORAGE_ENGINE=1 -DMYSQL_UNIX_ADDR==/usr/local/mysql/mysql.sock -DMYSQL_USER=mysql -DDEFAULT_CHARSET=utf8 -DDEFAULT_COLLATION=utf8_general_ci

......

-- Looking for asprintf - found

-- Check size of pthread_t

-- Check size of pthread_t - done

-- Using cmake version 2.6.4

-- Not building NDB

-- Performing Test HAVE_PEERCRED

-- Performing Test HAVE_PEERCRED - Success

-- Library mysqlclient depends on OSLIBS -lpthread;m;rt;dl

-- Googlemock was not found. gtest-based unit tests will be disabled. You can run cmake . -DENABLE_DOWNLOADS=1 to automatically download and build required components from source.

-- If you are inside a firewall, you may need to use an http proxy: export http_proxy=http://foo.bar.com:80

-- Library mysqlserver depends on OSLIBS -lpthread;m;rt;crypt;dl

-- Configuring done

-- Generating done

-- Build files have been written to: /root/mysql/mysql-5.6.12

real 0m45.943s

user 0m26.213s

sys 0m17.661s

time make

这一步时间比较长，需要耐心等待，看中间是否有error信息产生。

会看到很多Building信息

......

[ 38%] Building CXX object storage/innobase/CMakeFiles/innobase.dir/lock/lock0iter.cc.o

[ 38%] Building CXX object storage/innobase/CMakeFiles/innobase.dir/lock/lock0lock.cc.o

[ 38%] Building CXX object storage/innobase/CMakeFiles/innobase.dir/lock/lock0wait.cc.o

[ 38%] Building CXX object storage/innobase/CMakeFiles/innobase.dir/log/log0log.cc.o

[ 39%] Building CXX object storage/innobase/CMakeFiles/innobase.dir/log/log0recv.cc.o

[ 39%] Building CXX object storage/innobase/CMakeFiles/innobase.dir/mach/mach0data.cc.o

[ 39%] Building CXX object storage/innobase/CMakeFiles/innobase.dir/mem/mem0mem.cc.o

......

[100%] Building CXX object mysql-test/lib/My/SafeProcess/CMakeFiles/my_safe_process.dir/safe_process.cc.o

Linking CXX executable my_safe_process

[100%] Built target my_safe_process

real 21m39.375s

user 18m9.239s

sys 1m34.320s

time make install

这个命令比较快

......

-- Installing: /usr/local/mysql/man/man8/mysqld.8

-- Installing: /usr/local/mysql/support-files/solaris/postinstall-solaris

real 0m8.439s

user 0m3.353s

sys 0m4.616s

9 init db，初始化数据库

ll /home/data/mysql/data

cd /home/data/mysql/data

先赋予文件夹mysql权限

chown -R mysql /home/data/mysql/data

chgrp -R mysql /home/data/mysql/data

chown -R mysql /usr/local/mysql/

chgrp -R mysql /usr/local/mysql/

cd /usr/local/mysql/

cp support-files/my-default.cnf /etc/my56.cnf

scripts/mysql_install_db --user=mysql --basedir=/usr/local/mysql --datadir=/home/data/mysql/data --defaults-file=/usr/local/mysql/my.cnf

[root@localhost mysql]# scripts/mysql_install_db --user=mysql --basedir=/usr/local/mysql --datadir=/home/data/mysql/data --defaults-file=/usr/local/mysql/my.cnf

Installing MySQL system tables.../usr/local/mysql/bin/mysqld: File '/home/data/mysql/binlog/mysql-bin.index' not found (Errcode: 2 - No such file or directory)

2014-06-27 10:47:14 9686 [ERROR] Aborting

2014-06-27 10:47:14 9686 [Note] Binlog end

2014-06-27 10:47:14 9686 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete

[root@localhost mysql]# mkdir -p /home/data/mysql/binlog/

[root@localhost mysql]#

[root@localhost mysql]# chown -R mysql /home/data/mysql/binlog/

[root@localhost mysql]# chgrp -R mysql /home/data/mysql/binlog/

建好目录，再执行数据库初始化：

[root@472322 mysql56]# scripts/mysql_install_db --user=mysql --basedir=/usr/local/mysql --datadir=/home/data/mysql/data --defaults-file=/usr/local/mysql/my.cnf

Installing MySQL system tables...2013-08-22 05:06:03 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

2013-08-22 05:06:03 19416 [Note] InnoDB: The InnoDB memory heap is disabled

2013-08-22 05:06:03 19416 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2013-08-22 05:06:03 19416 [Note] InnoDB: Compressed tables use zlib 1.2.3

2013-08-22 05:06:03 19416 [Note] InnoDB: Using CPU crc32 instructions

2013-08-22 05:06:03 19416 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2013-08-22 05:06:03 19416 [Note] InnoDB: Completed initialization of buffer pool

2013-08-22 05:06:03 19416 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!

2013-08-22 05:06:03 19416 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB

2013-08-22 05:06:03 19416 [Note] InnoDB: Database physically writes the file full: wait...

2013-08-22 05:06:03 19416 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB

2013-08-22 05:06:03 19416 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB

2013-08-22 05:06:03 19416 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0

2013-08-22 05:06:03 19416 [Warning] InnoDB: New log files created, LSN=45781

2013-08-22 05:06:03 19416 [Note] InnoDB: Doublewrite buffer not found: creating new

2013-08-22 05:06:03 19416 [Note] InnoDB: Doublewrite buffer created

2013-08-22 05:06:03 19416 [Note] InnoDB: 128 rollback segment(s) are active.

2013-08-22 05:06:03 19416 [Warning] InnoDB: Creating foreign key constraint system tables.

2013-08-22 05:06:03 19416 [Note] InnoDB: Foreign key constraint system tables created

2013-08-22 05:06:03 19416 [Note] InnoDB: Creating tablespace and datafile system tables.

2013-08-22 05:06:03 19416 [Note] InnoDB: Tablespace and datafile system tables created.

2013-08-22 05:06:03 19416 [Note] InnoDB: Waiting for purge to start

2013-08-22 05:06:03 19416 [Note] InnoDB: 5.6.13 started; log sequence number 0

2013-08-22 05:06:04 19416 [Note] Binlog end

2013-08-22 05:06:04 19416 [Note] InnoDB: FTS optimize thread exiting.

2013-08-22 05:06:04 19416 [Note] InnoDB: Starting shutdown...

2013-08-22 05:06:05 19416 [Note] InnoDB: Shutdown completed; log sequence number 1625977

Filling help tables...2013-08-22 05:06:05 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

2013-08-22 05:06:05 19439 [Note] InnoDB: The InnoDB memory heap is disabled

2013-08-22 05:06:05 19439 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2013-08-22 05:06:05 19439 [Note] InnoDB: Compressed tables use zlib 1.2.3

2013-08-22 05:06:05 19439 [Note] InnoDB: Using CPU crc32 instructions

2013-08-22 05:06:05 19439 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2013-08-22 05:06:05 19439 [Note] InnoDB: Completed initialization of buffer pool

2013-08-22 05:06:05 19439 [Note] InnoDB: Highest supported file format is Barracuda.

2013-08-22 05:06:05 19439 [Note] InnoDB: 128 rollback segment(s) are active.

2013-08-22 05:06:05 19439 [Note] InnoDB: Waiting for purge to start

2013-08-22 05:06:05 19439 [Note] InnoDB: 5.6.13 started; log sequence number 1625977

2013-08-22 05:06:05 19439 [Note] Binlog end

2013-08-22 05:06:05 19439 [Note] InnoDB: FTS optimize thread exiting.

2013-08-22 05:06:05 19439 [Note] InnoDB: Starting shutdown...

2013-08-22 05:06:06 19439 [Note] InnoDB: Shutdown completed; log sequence number 1625987

To start mysqld at boot time you have to copy

support-files/mysql.server to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !

To do so, start the server, then issue the following commands:

/usr/local/mysql56/bin/mysqladmin -u root password 'new-password'

/usr/local/mysql56/bin/mysqladmin -u root -h 472322.ea.com password 'new-password'

Alternatively you can run:

/usr/local/mysql56/bin/mysql_secure_installation

which will also give you the option of removing the test

databases and anonymous user created by default. This is

strongly recommended for production servers.

See the manual for more instructions.

You can start the MySQL daemon with:

cd . ; /usr/local/mysql56/bin/mysqld_safe &

You can test the MySQL daemon with mysql-test-run.pl

cd mysql-test ; perl mysql-test-run.pl

Please report any problems with the ./bin/mysqlbug script!

The latest information about MySQL is available on the web at

http://www.mysql.com

Support MySQL by buying support/licenses at http://shop.mysql.com

New default config file was created as /usr/local/mysql56/my.cnf and

will be used by default by the server when you start it.

You may edit this file to change server settings

WARNING: Default config file /etc/my.cnf exists on the system

This file will be read by default by the MySQL server

If you do not want to use this, either remove it, or use the

--defaults-file argument to mysqld_safe when starting the server

[root@472322 mysql56]#

10 copy start command

cp support-files/mysql.server /etc/init.d/mysqld5612

chmod 700 /etc/init.d/mysqld5612

echo "export PATH=$PATH:/usr/local/mysql/bin">>/etc/profile

source /etc/profile

11 添加开机启动

chkconfig --add mysqld5612

12 start service

service mysqld5612 start

[root@squid-2 mysql]# service mysqld5612 start

Starting MySQL.......The server quit without updating PID f[失败]usr/local/mysql/mysqld.pid).

[root@squid-2 mysql]#

查看日志报错如下：

2014-06-24 14:56:54 31726 [Note] Server socket created on IP: '::'.

2014-06-24 14:56:54 31726 [ERROR] Can't start server : Bind on unix socket: Permission denied

2014-06-24 14:56:54 31726 [ERROR] Do you already have another mysqld server running on socket: /usr/local/mysql/mysql.sock ?

2014-06-24 14:56:54 31726 [ERROR] Aborting

解决原因是:

/usr/local/mysql跟目录需要赋予mysql权限

根据日志文件显示，首先检查运行权限，再看一下/usr/local/mysql/mysql.sock，发现/usr/local/mysql目录下并没有该文件，是否是没有权限写目录？

看到/usr/local/mysql目录是root用户，所以赋予mysql操作权限。

chown -R mysql.mysql /usr/local/mysql

[root@472322 data56]# service mysqld5612 start

Starting MySQL. SUCCESS!

[root@472322 data56]# mysql

Welcome to the MySQL monitor. Commands end with ; or /g.

Your MySQL connection id is 1

Server version: 5.6.13 Source distribution

Oracle is a registered trademark of Oracle Corporation and/or its

affiliates. Other names may be trademarks of their respective

owners.

Type 'help;' or '/h' for help. Type '/c' to clear the current input statement.

mysql> show databases;

+--------------------+

| Database |

+--------------------+

| information_schema |

| mysql |

| performance_schema |

| test |

+--------------------+

4 rows in set (0.00 sec)

mysql>

Statement

The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Explain the role of InnoDB redo logs and undo logs.Apr 15, 2025 am 12:16 AM

InnoDB uses redologs and undologs to ensure data consistency and reliability. 1.redologs record data page modification to ensure crash recovery and transaction persistence. 2.undologs records the original data value and supports transaction rollback and MVCC.

What are the key metrics to look for in an EXPLAIN output (type, key, rows, Extra)?Apr 15, 2025 am 12:15 AM

Key metrics for EXPLAIN commands include type, key, rows, and Extra. 1) The type reflects the access type of the query. The higher the value, the higher the efficiency, such as const is better than ALL. 2) The key displays the index used, and NULL indicates no index. 3) rows estimates the number of scanned rows, affecting query performance. 4) Extra provides additional information, such as Usingfilesort prompts that it needs to be optimized.

What is the Using temporary status in EXPLAIN and how to avoid it?Apr 15, 2025 am 12:14 AM

Usingtemporary indicates that the need to create temporary tables in MySQL queries, which are commonly found in ORDERBY using DISTINCT, GROUPBY, or non-indexed columns. You can avoid the occurrence of indexes and rewrite queries and improve query performance. Specifically, when Usingtemporary appears in EXPLAIN output, it means that MySQL needs to create temporary tables to handle queries. This usually occurs when: 1) deduplication or grouping when using DISTINCT or GROUPBY; 2) sort when ORDERBY contains non-index columns; 3) use complex subquery or join operations. Optimization methods include: 1) ORDERBY and GROUPB

Describe the different SQL transaction isolation levels (Read Uncommitted, Read Committed, Repeatable Read, Serializable) and their implications in MySQL/InnoDB.Apr 15, 2025 am 12:11 AM

MySQL/InnoDB supports four transaction isolation levels: ReadUncommitted, ReadCommitted, RepeatableRead and Serializable. 1.ReadUncommitted allows reading of uncommitted data, which may cause dirty reading. 2. ReadCommitted avoids dirty reading, but non-repeatable reading may occur. 3.RepeatableRead is the default level, avoiding dirty reading and non-repeatable reading, but phantom reading may occur. 4. Serializable avoids all concurrency problems but reduces concurrency. Choosing the appropriate isolation level requires balancing data consistency and performance requirements.

MySQL vs. Other Databases: Comparing the OptionsApr 15, 2025 am 12:08 AM

MySQL is suitable for web applications and content management systems and is popular for its open source, high performance and ease of use. 1) Compared with PostgreSQL, MySQL performs better in simple queries and high concurrent read operations. 2) Compared with Oracle, MySQL is more popular among small and medium-sized enterprises because of its open source and low cost. 3) Compared with Microsoft SQL Server, MySQL is more suitable for cross-platform applications. 4) Unlike MongoDB, MySQL is more suitable for structured data and transaction processing.

How does MySQL index cardinality affect query performance?Apr 14, 2025 am 12:18 AM

MySQL index cardinality has a significant impact on query performance: 1. High cardinality index can more effectively narrow the data range and improve query efficiency; 2. Low cardinality index may lead to full table scanning and reduce query performance; 3. In joint index, high cardinality sequences should be placed in front to optimize query.

MySQL: Resources and Tutorials for New UsersApr 14, 2025 am 12:16 AM

The MySQL learning path includes basic knowledge, core concepts, usage examples, and optimization techniques. 1) Understand basic concepts such as tables, rows, columns, and SQL queries. 2) Learn the definition, working principles and advantages of MySQL. 3) Master basic CRUD operations and advanced usage, such as indexes and stored procedures. 4) Familiar with common error debugging and performance optimization suggestions, such as rational use of indexes and optimization queries. Through these steps, you will have a full grasp of the use and optimization of MySQL.

Real-World MySQL: Examples and Use CasesApr 14, 2025 am 12:15 AM

MySQL's real-world applications include basic database design and complex query optimization. 1) Basic usage: used to store and manage user data, such as inserting, querying, updating and deleting user information. 2) Advanced usage: Handle complex business logic, such as order and inventory management of e-commerce platforms. 3) Performance optimization: Improve performance by rationally using indexes, partition tables and query caches.

See all articles