Home Database Mysql Tutorial 源码编译安装MySQL5.6.12详细过程_MySQL

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

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

ok

[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

OK

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

OK

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

Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.

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 of this Website
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

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

Notepad++7.3.1

Notepad++7.3.1

Easy-to-use and free code editor

SublimeText3 Chinese version

SublimeText3 Chinese version

Chinese version, very easy to use

Zend Studio 13.0.1

Zend Studio 13.0.1

Powerful PHP integrated development environment

Dreamweaver CS6

Dreamweaver CS6

Visual web development tools

SublimeText3 Mac version

SublimeText3 Mac version

God-level code editing software (SublimeText3)

When might a full table scan be faster than using an index in MySQL? When might a full table scan be faster than using an index in MySQL? Apr 09, 2025 am 12:05 AM

Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.

Can I install mysql on Windows 7 Can I install mysql on Windows 7 Apr 08, 2025 pm 03:21 PM

Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.

Explain InnoDB Full-Text Search capabilities. Explain InnoDB Full-Text Search capabilities. Apr 02, 2025 pm 06:09 PM

InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.

Difference between clustered index and non-clustered index (secondary index) in InnoDB. Difference between clustered index and non-clustered index (secondary index) in InnoDB. Apr 02, 2025 pm 06:25 PM

The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values ​​and pointers to data rows, and is suitable for non-primary key column queries.

MySQL: Simple Concepts for Easy Learning MySQL: Simple Concepts for Easy Learning Apr 10, 2025 am 09:29 AM

MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.

Explain different types of MySQL indexes (B-Tree, Hash, Full-text, Spatial). Explain different types of MySQL indexes (B-Tree, Hash, Full-text, Spatial). Apr 02, 2025 pm 07:05 PM

MySQL supports four index types: B-Tree, Hash, Full-text, and Spatial. 1.B-Tree index is suitable for equal value search, range query and sorting. 2. Hash index is suitable for equal value searches, but does not support range query and sorting. 3. Full-text index is used for full-text search and is suitable for processing large amounts of text data. 4. Spatial index is used for geospatial data query and is suitable for GIS applications.

The relationship between mysql user and database The relationship between mysql user and database Apr 08, 2025 pm 07:15 PM

In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.

Can mysql and mariadb coexist Can mysql and mariadb coexist Apr 08, 2025 pm 02:27 PM

MySQL and MariaDB can coexist, but need to be configured with caution. The key is to allocate different port numbers and data directories to each database, and adjust parameters such as memory allocation and cache size. Connection pooling, application configuration, and version differences also need to be considered and need to be carefully tested and planned to avoid pitfalls. Running two databases simultaneously can cause performance problems in situations where resources are limited.

See all articles