搜索
首页数据库mysql教程源码编译安装MySQL5.6.12详细过程_MySQL

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> 

声明
本文内容由网友自发贡献,版权归原作者所有,本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容,请联系admin@php.cn
说明InnoDB重做日志和撤消日志的作用。说明InnoDB重做日志和撤消日志的作用。Apr 15, 2025 am 12:16 AM

InnoDB使用redologs和undologs确保数据一致性和可靠性。1.redologs记录数据页修改,确保崩溃恢复和事务持久性。2.undologs记录数据原始值,支持事务回滚和MVCC。

在解释输出(类型,键,行,额外)中要查找的关键指标是什么?在解释输出(类型,键,行,额外)中要查找的关键指标是什么?Apr 15, 2025 am 12:15 AM

EXPLAIN命令的关键指标包括type、key、rows和Extra。1)type反映查询的访问类型,值越高效率越高,如const优于ALL。2)key显示使用的索引,NULL表示无索引。3)rows预估扫描行数,影响查询性能。4)Extra提供额外信息,如Usingfilesort提示需要优化。

在解释中使用临时状态以及如何避免它是什么?在解释中使用临时状态以及如何避免它是什么?Apr 15, 2025 am 12:14 AM

Usingtemporary在MySQL查询中表示需要创建临时表,常见于使用DISTINCT、GROUPBY或非索引列的ORDERBY。可以通过优化索引和重写查询避免其出现,提升查询性能。具体来说,Usingtemporary出现在EXPLAIN输出中时,意味着MySQL需要创建临时表来处理查询。这通常发生在以下情况:1)使用DISTINCT或GROUPBY时进行去重或分组;2)ORDERBY包含非索引列时进行排序;3)使用复杂的子查询或联接操作。优化方法包括:1)为ORDERBY和GROUPB

描述不同的SQL交易隔离级别(读取未读取,读取,可重复的读取,可序列化)及其在MySQL/InnoDB中的含义。描述不同的SQL交易隔离级别(读取未读取,读取,可重复的读取,可序列化)及其在MySQL/InnoDB中的含义。Apr 15, 2025 am 12:11 AM

MySQL/InnoDB支持四种事务隔离级别:ReadUncommitted、ReadCommitted、RepeatableRead和Serializable。1.ReadUncommitted允许读取未提交数据,可能导致脏读。2.ReadCommitted避免脏读,但可能发生不可重复读。3.RepeatableRead是默认级别,避免脏读和不可重复读,但可能发生幻读。4.Serializable避免所有并发问题,但降低并发性。选择合适的隔离级别需平衡数据一致性和性能需求。

MySQL与其他数据库:比较选项MySQL与其他数据库:比较选项Apr 15, 2025 am 12:08 AM

MySQL适合Web应用和内容管理系统,因其开源、高性能和易用性而受欢迎。1)与PostgreSQL相比,MySQL在简单查询和高并发读操作上表现更好。2)相较Oracle,MySQL因开源和低成本更受中小企业青睐。3)对比MicrosoftSQLServer,MySQL更适合跨平台应用。4)与MongoDB不同,MySQL更适用于结构化数据和事务处理。

MySQL索引基数如何影响查询性能?MySQL索引基数如何影响查询性能?Apr 14, 2025 am 12:18 AM

MySQL索引基数对查询性能有显着影响:1.高基数索引能更有效地缩小数据范围,提高查询效率;2.低基数索引可能导致全表扫描,降低查询性能;3.在联合索引中,应将高基数列放在前面以优化查询。

MySQL:新用户的资源和教程MySQL:新用户的资源和教程Apr 14, 2025 am 12:16 AM

MySQL学习路径包括基础知识、核心概念、使用示例和优化技巧。1)了解表、行、列、SQL查询等基础概念。2)学习MySQL的定义、工作原理和优势。3)掌握基本CRUD操作和高级用法,如索引和存储过程。4)熟悉常见错误调试和性能优化建议,如合理使用索引和优化查询。通过这些步骤,你将全面掌握MySQL的使用和优化。

现实世界Mysql:示例和用例现实世界Mysql:示例和用例Apr 14, 2025 am 12:15 AM

MySQL在现实世界的应用包括基础数据库设计和复杂查询优化。1)基本用法:用于存储和管理用户数据,如插入、查询、更新和删除用户信息。2)高级用法:处理复杂业务逻辑,如电子商务平台的订单和库存管理。3)性能优化:通过合理使用索引、分区表和查询缓存来提升性能。

See all articles

热AI工具

Undresser.AI Undress

Undresser.AI Undress

人工智能驱动的应用程序,用于创建逼真的裸体照片

AI Clothes Remover

AI Clothes Remover

用于从照片中去除衣服的在线人工智能工具。

Undress AI Tool

Undress AI Tool

免费脱衣服图片

Clothoff.io

Clothoff.io

AI脱衣机

AI Hentai Generator

AI Hentai Generator

免费生成ai无尽的。

热门文章

R.E.P.O.能量晶体解释及其做什么(黄色晶体)
4 周前By尊渡假赌尊渡假赌尊渡假赌
R.E.P.O.最佳图形设置
4 周前By尊渡假赌尊渡假赌尊渡假赌
R.E.P.O.如果您听不到任何人,如何修复音频
4 周前By尊渡假赌尊渡假赌尊渡假赌
R.E.P.O.聊天命令以及如何使用它们
4 周前By尊渡假赌尊渡假赌尊渡假赌

热工具

SublimeText3汉化版

SublimeText3汉化版

中文版,非常好用

Atom编辑器mac版下载

Atom编辑器mac版下载

最流行的的开源编辑器

VSCode Windows 64位 下载

VSCode Windows 64位 下载

微软推出的免费、功能强大的一款IDE编辑器

禅工作室 13.0.1

禅工作室 13.0.1

功能强大的PHP集成开发环境

DVWA

DVWA

Damn Vulnerable Web App (DVWA) 是一个PHP/MySQL的Web应用程序,非常容易受到攻击。它的主要目标是成为安全专业人员在合法环境中测试自己的技能和工具的辅助工具,帮助Web开发人员更好地理解保护Web应用程序的过程,并帮助教师/学生在课堂环境中教授/学习Web应用程序安全。DVWA的目标是通过简单直接的界面练习一些最常见的Web漏洞,难度各不相同。请注意,该软件中