陆陆续续编写翻译php5

软件版本:php-5.4.27

依赖库:zlib,libxml2

交叉编译器:arm-hisiv200-linux-gnueabi

  1. 将陆续编写翻译器路线增添到PATH中,
    笔者的交叉编写翻译器目录为/usr/local/arm-hisiv200-linux/,而交叉编写翻译器在陆陆续续编写翻译器目录的/bin中,在决定台输入

    PATH=$PATH:/usr/local/arm-hisiv200-linux/bin/
    
  2. 率先先交叉编写翻译zlib,步向zlib源码目录。

  3. 执行CC=arm-hisiv200-linux-gnueabi-gcc  ./configure  –shared
     –prefix=ZLIB_PATH(编写翻译成功后的装置路线卡塔尔国
  4. make && make install
  5. 在ZLIB_PATH中会有编译成功后的公文和构造。
  6. 下一场交叉编译libxml2,步入libxml2源码目录。
  7. 执行CC=arm-hisiv200-linux-gnueabi-gcc  ./configure
     –host=arm-hisiv200-linux-gnueabi
     –prefix=LIBXML2_PATH(编写翻译成功后的装置路线State of Qatar
  8. make && make install
  9. 在LIBXML2_PATH中会有编写翻译成功后的公文和配备。
  10. 开端陆续编译php5,走入php5源码目录。
  11. 率先先实践./buildconf  –force,为了幸免现身 cp:cannot stat
    ‘sapi/cli/php.1′: No such file or directory
  12. 执行./configure  –host=arm-hisiv200-linux-gnueabi  –enable-shared
     –with-zlib-dir=ZLIB_PATH  –with-libxml-dir=LIBXML2_PATH
     –disable-phar  –with-sqlite  –with-pdo-sqlite  –without-iconv
     –enable-fpm  –prefix=PHP5_PATH
  13. make && make install
  14. 编译好的php程序及构培养在PHP5_PATH中。

ubuntu16 下 源码配置Lnmp境况,ubuntu16lnmp

今天把系统晋级到 ubuntu16悠远支持版 ,重新陈设了lnmp景况

约定多少个目录  源码目录  /usr/local/src 

                   mysql     /usr/local/mysql

                    php   /usr/local/php

                   nginx   /usr/local/nginx 

断断续续编写翻译nginx

软件版本:nginx-1.6.2

依附源码:pcre,zlib(这里是急需选拔它们的源码State of Qatar

陆陆续续编写翻译器:arm-hisiv200-linux-gnueabi

linux版本:叁十五位ubuntu(那个很珍视,重倘若利用叁十人x86系统本领拓宽编写翻译成功,因为字长不等同State of Qatar

陆续编写翻译nginx与接力编写翻译php5不一致便是nginx用的是依据的库的源码,而php5用的是库文件。

  1. 进去nginx-1.6.2源码目录。
  2. 在配备和编译nginx会现身过多八花九裂,大家一个二个缓解,首先本身使用的configure配置如下:

    #!/bin/bash
    
    CC_PATH=/home/shanlink/Cross_compile/arm-hisiv200-linux/bin/arm-hisiv200-linux-gnueabi-gcc
    CPP_PATH=/home/shanlink/Cross_compile/arm-hisiv200-linux/bin/arm-hisiv200-linux-gnueabi-g++
    INSTALL_PATH=/home/shanlink/Cross_compile/nginx_ccs/
    PCRE_PATH=/home/shanlink/Cross_compile/pcre-8.11/
    ZLIB_PATH=/home/shanlink/Cross_compile/zlib-1.2.3/
    CC_OPTS="-I /home/shanlink/Cross_compile/arm-hisiv200-linux/target/include/"
    
    ./configure --prefix=$INSTALL_PATH --with-zlib=$ZLIB_PATH --with-pcre=$PCRE_PATH --with-cc=$CC_PATH --with-cpp=$CPP_PATH --with-cc-opt=$CC_POTS --with-ld-opt="-L /home/shanlink/Cross_compile/arm-hisiv200-linux/target/lib/"
    
  3. 好的,把上述内容做成三个运营脚本,运维,现身叁个八花九裂:

    checking for OS
     + Linux 3.13.0-43-generic x86_64
    checking for C compiler ... found but is not working
    
    ./configure: error: C compiler /home/shanlink/Cross_compile/arm-hisiv200-linux/bin/arm-hisiv200-linux-gnueabi-gcc is not found
    

    消除办法正是:编辑auto/cc/name文件,在文件带头好似下一段,注释掉exit
    1

    if [ "$NGX_PLATFORM" != win32 ]; then
    
        ngx_feature="C compiler"
        ngx_feature_name=
        ngx_feature_run=yes
        ngx_feature_incs=
        ngx_feature_path=
        ngx_feature_libs=
        ngx_feature_test=
        . auto/feature
    
        if [ $ngx_found = no ]; then
            echo
            echo $0: error: C compiler $CC is not found
            echo
            #exit 1        注释掉这一行     
        fi
    
    fi
    
  4. 再也运维大家的布置脚本,当时现身

    checking for TCP_INFO ... found
    checking for accept4() ... found
    checking for int size ...objs/autotest: 1: objs/autotest: Syntax error: word unexpected (expecting ")")
      bytes
    
    ./configure: error: can not detect int size
    cat: objs/autotest.c: No such file or directory
    

    消除措施:编辑auto/types/sizeof文件,找到

    ngx_test="$CC $CC_TEST_FLAGS $CC_AUX_FLAGS \
              -o $NGX_AUTOTEST $NGX_AUTOTEST.c $NGX_LD_OPT $ngx_feature_libs"
    
    将的$CC改为x86上使用的gcc
    
    ngx_test="gcc $CC_TEST_FLAGS $CC_AUX_FLAGS \
              -o $NGX_AUTOTEST $NGX_AUTOTEST.c $NGX_LD_OPT $ngx_feature_libs"
    
  5. 再也运维我们的布署脚本,这时候应该能够顺遂配置完成。

  6. 进行make,当时会现出一个谬误

    checking for C compiler default output file name... a.out
    checking for suffix of executables... 
    checking whether we are cross compiling... configure: error: in `/home/shanlink/Cross_compile/pcre-8.11':
    configure: error: cannot run C compiled programs.
    If you meant to cross compile, use `--host'.
    See `config.log' for more details.
    make[1]: *** [/home/shanlink/Cross_compile/pcre-8.11//Makefile] Error 1
    make[1]: Leaving directory `/home/shanlink/Cross_compile/nginx-1.6.2'
    make: *** [build] Error 2
    

    其一是出于nginx在编译时会同期安排pcre并且打开编写翻译,而由于是交叉编写翻译,pcre的配置时必要增多–host=arm-hisiv200-linux-gnueabi,因为是由nginx自动配置的,所以大家必要手动增多此选项于pcre,然后再make,此选项增多在

    文件:objs/Makefile
    
    找到如下一段:
    /home/shanlink/Cross_compile/pcre-8.11//Makefile:    objs/Makefile
        cd /home/shanlink/Cross_compile/pcre-8.11/ \
        && if [ -f Makefile ]; then $(MAKE) distclean; fi \
        && CC="$(CC)" CFLAGS="-O2 -fomit-frame-pointer -pipe " \
        ./configure --disable-shared 
    
    将
        ./configure --disable-shared 
    改为
        ./configure --disable-shared --host=arm-hisiv200-linux-gnueabi(这个交叉编译器前缀填你们电脑上自己的)
    
  7. 借使超过一下破绽非常多,原因是你们的linux系统是61个人的,而arm上肖似都以三拾一位的,所以会有其一荒谬,解除办法正是再次装三个三11个人的linux系统。

    src/core/ngx_slab.c: In function 'ngx_slab_alloc_locked':
    src/core/ngx_slab.c:209: error: integer constant is too large for 'long' type
    src/core/ngx_slab.c:209: error: comparison is always true due to limited range of data type
    src/core/ngx_slab.c:221: error: integer constant is too large for 'long' type
    src/core/ngx_slab.c:221: error: comparison is always false due to limited range of data type
    src/core/ngx_slab.c:223: error: integer constant is too large for 'long' type
    src/core/ngx_slab.c:223: error: comparison is always true due to limited range of data type
    src/core/ngx_slab.c:253: error: integer constant is too large for 'long' type
    src/core/ngx_slab.c:253: error: comparison is always true due to limited range of data type
    src/core/ngx_slab.c:262: error: integer constant is too large for 'long' type
    src/core/ngx_slab.c:262: error: comparison is always false due to limited range of data type
    src/core/ngx_slab.c:289: error: left shift count >= width of type
    src/core/ngx_slab.c:292: error: integer constant is too large for 'long' type
    src/core/ngx_slab.c:294: error: left shift count >= width of type
    src/core/ngx_slab.c:304: error: integer constant is too large for 'long' type
    src/core/ngx_slab.c:376: error: left shift count >= width of type
    src/core/ngx_slab.c: In function 'ngx_slab_free_locked':
    src/core/ngx_slab.c:499: error: integer constant is too large for 'long' type
    src/core/ngx_slab.c:499: error: comparison is always false due to limited range of data type
    src/core/ngx_slab.c:552: error: integer constant is too large for 'long' type
    src/core/ngx_slab.c:575: error: integer constant is too large for 'long' type
    src/core/ngx_slab.c:575: error: comparison is always false due to limited range of data type
    src/core/ngx_slab.c:582: error: integer constant is too large for 'long' type
    src/core/ngx_slab.c: In function 'ngx_slab_alloc_pages':
    src/core/ngx_slab.c:643: error: integer constant is too large for 'long' type
    src/core/ngx_slab.c:652: error: integer constant is too large for 'long' type
    src/core/ngx_slab.c:652: error: large integer implicitly truncated to unsigned type
    make[1]: *** [objs/src/core/ngx_slab.o] Error 1
    make[1]: Leaving directory `/home/shanlink/Cross_compile/nginx-1.6.2'
    make: *** [build] Error 2
    
  8. 那会儿继续make,还也许会现出多少个错误,二个是

    src/os/unix/ngx_errno.c: In function 'ngx_strerror':
    src/os/unix/ngx_errno.c:37: error: 'NGX_SYS_NERR' undeclared (first use in this function)
    src/os/unix/ngx_errno.c:37: error: (Each undeclared identifier is reported only once
    src/os/unix/ngx_errno.c:37: error: for each function it appears in.)
    src/os/unix/ngx_errno.c: In function 'ngx_strerror_init':
    src/os/unix/ngx_errno.c:58: error: 'NGX_SYS_NERR' undeclared (first use in this function)
    make[1]: *** [objs/src/os/unix/ngx_errno.o] Error 1
    make[1]: Leaving directory `/home/shanlink/Cross_compile/nginx-1.6.2'
    make: *** [build] Error 2
    

    化解方法正是开发objs/ngx_auto_config.h,添加

    #ifndef NGX_SYS_NERR
    #define NGX_SYS_NERR    132
    #endif
    

    另一个八花九裂

    objs/src/event/ngx_event_accept.o: In function `ngx_event_accept':
    /home/shanlink/Cross_compile/nginx-1.6.2/src/event/ngx_event_accept.c:64: warning: warning: accept4 is not implemented and will always fail
    objs/src/core/ngx_cycle.o: In function `ngx_init_cycle':
    /home/shanlink/Cross_compile/nginx-1.6.2/src/core/ngx_cycle.c:457: undefined reference to `ngx_shm_free'
    /home/shanlink/Cross_compile/nginx-1.6.2/src/core/ngx_cycle.c:462: undefined reference to `ngx_shm_alloc'
    /home/shanlink/Cross_compile/nginx-1.6.2/src/core/ngx_cycle.c:648: undefined reference to `ngx_shm_free'
    objs/src/event/ngx_event.o: In function `ngx_event_module_init':
    /home/shanlink/Cross_compile/nginx-1.6.2/src/event/ngx_event.c:525: undefined reference to `ngx_shm_alloc'
    collect2: ld returned 1 exit status
    make[1]: *** [objs/nginx] Error 1
    make[1]: Leaving directory `/home/shanlink/Cross_compile/nginx-1.6.2'
    make: *** [build] Error 2
    shanlink@ubuntu:~/Cross_compile
    

    同等的,大家供给改进objs/ngx_auto_config.h文件,在文书中投入

    #ifndef NGX_HAVE_SYSVSHM
    #define NGX_HAVE_SYSVSHM 1
    #endif
    
  9. 好了,当时make && make install就应当能编译过去了。

  10. 若是境遇任何编写翻译难点,请参谋:

 

时有时无编写翻译squid

软件版本:squid-2.7-STABLE9

接力编写翻译器:arm-hisiv200-linux-gnueabi

系统:32位ubuntu

在对squid进行接力编译时,供给使用x86版本的squid,所以大家要开展五个本子的编写翻译。

  1. 率先编写翻译x86本子的行使计划为

    ./configure --prefix=X86_SQUID_PATH
    
  2. make && make install

  3. 步向到squid源码目录下的src/文件夹,有个cf_gen程序,备份起来,交叉编写翻译时会用到。
  4. 树立三个arm-linux.cache文件,写入

    ac_cv_epoll_works=
    ac_cv_af_unix_large_dgram=
    ac_cv_func_setresuid=
    ac_cv_func_va_copy=
    ac_cv_func___va_copy=
    
  5. 执行

    #!/bin/bash
    
    ./configure --host=arm-hisiv200-linux-gnueabi --prefix=/home/shanlink/Cross_compile/squid_ccs/ --cache-file=arm-linux.cache
    

    那时候应该是能够如愿经过的

  6. 举行make,会现身三个八花九裂

    ./cf_gen: cannot execute binary file
    
  7. 将此前备份的x86的cf_gen复制到src/目录下替换arm的

  8. 再次实施make,应该能够高枕而卧经过编写翻译
  9. make install
  10. 完成

mysql   版本 5.7.14

 

必备的包和工具

gcc/g++ :MySQL 5.6始发,须求使用g++实行编写翻译。

bison  :MySQL语法剖判器须求运用bison进行编写翻译。

libncurses5-dev
:用于终端操作的支出包.(注:Debian/Ubuntu下供给安装libncurses5-dev;Redhat下要求安装
ncurses-develState of Qatar
zlib    :MySQL使用zlib实行减少

 

功能需求的包

libxml2  :用于XML输入输出方式的辅助。

openssl  :使用openssl保险套接字情势通讯。

dtrace  :用于确诊MySQL难点。

cmake  :MySQL 5.5开端,使用cmake实行工程管理,cmake需求2.8之上版本。

 

sudo apt-get install gcc

sudo apt-get install libxml2

sudo apt-get install  libncurses5-dev bison 

设置cmake      下载地址  

 

创造源码包目录

mkdir /usr/local/src

 

解压

tar zxvf cmake-3.6.1.tar.gz 

mv cmake-3.6.1 /usr/local/src

cd cmake-3.6.1

 

编写翻译安装

./configure   make && make install

 

插手情形变量

vim ~/.bashrc

添加

export PATH=”/usr/local/src/cmake-3.6.1/bin/cmake:$PATH”

 

从MySQL
5.7.5起头Boost库是必备的,下载Boost库 

tar zxvf boost_1_59_0.tar.gz 

mv boost_1_59_0 /usr/local/

 

成立Mysql系统客户组和客户,及数据库贮存目录:

mkdir -p /usr/local/mysql/

mkdir -p /usr/local/mysql/data/

 

依靠须求其余创立mysql socket
文件保留目录,纵然要重复内定寄放地方,必要重新编译

groupadd mysql    添加mysql 用户组

useradd mysql -g mysql  添加mysql用户 并指定mysql用户组

chown -PAJERO mysql:mysql /usr/local/mysql/
 改换钦定目录以致其子目录下放权力限为mysql客商和mysql客户组

 

mysql官方下载地址

   分选可编写翻译版本

tar zxvf mysql-5.7.14.tar.gz

cd mysql-5.7.14

编译

cmake . -DCMAKE_INSTALL_PREFIX=/usr/local/mysql
-DMYSQL_DATADIR=/usr/local/mysql/data
-DWITH_INNOBASE_STORAGE_ENGINE=1 -DWITH_ARCHIVE_STORAGE_ENGINE=1
-DWITH_BLACKHOLE_STORAGE_ENGINE=1
-DWITH_PARTITION_STORAGE_ENGINE=1
-DWITH_PERFSCHEMA_STORAGE_ENGINE=1
-DWITHOUT_EXAMPLE_STORAGE_ENGINE=1
-DWITHOUT_FEDERATED_STORAGE_ENGINE=1 -DDEFAULT_CHARSET=utf8
-DDEFAULT_COLLATION=utf8_general_ci -DWITH_EXTRA_CHARSETS=all
-DENABLED_LOCAL_INFILE=1
 -DMYSQL_UNIX_ADDR=/usr/local/mysql/data/mysql.sock
-DCOMPILATION_COMMENT=”string”-DENABLED_PROFILING=1
-DOPTIMIZER_TRACE=1 -DWITH_DEBUG=1 -DWITH_BOOST=/usr/local/boost

make && make install

 

创办数据库服务

在5.5和5.6版本中,mysql数据库是接纳mysqld_db_install命令进行初步化的;在5.7过后,数据库起先化发生了改动,须要mysqld命令实行最初化:

/usr/local/mysql/bin/mysqld  –initialize   –user=mysql
 –basedir=/usr/local/mysql –datadir=/usr/local/mysql/data/

—以root最早化操作时要加–user=mysql参数,生成叁个即兴密码(注意保存登陆时用)

数据库初步化后,再度修改权限:

chown -R mysql:mysql /usr/local/mysql/data  

 

打算布置文件并运转mysql服务

复制暗许配置文件到/etc

cp /usr/local/mysql/support-files/my-default.cnf /etc/my.cnf

变动文件权限为mysql 客户和组

sudo chown mysql:mysql /etc/my.cnf

大约改善一下安顿文件

vim /etc/my.cnf

[client]
port = 3306
socket = /usr/local/mysql/data/mysql.sock

[mysqld]
port = 3306
socket = /usr/local/mysql/data/mysql.sock
basedir = /usr/local/mysql
datadir  = /usr/local/mysql/data

 

后台运营mysql

/usr/local/mysql/bin/mysqld_safe –user –defaults-file/etc/my.cnf

 

查看mysql 端口或进度

netstat -altn | grep 3306 或  ps -ef|grep mysql

tcp6       0      0 :::3306                 :::*                  
 LISTEN 

 

用起来随机密码登陆后更改密码

/usr/local/mysql/bin/mysql -uroot -p

mysql> set password for
[email protected]=password(‘新密码’);

Query OK, 0 rows affected, 1 warning (0.00 sec)

 

累积服务,复制运维脚本到/etc/init.d目录

cd /usr/local/mysql/
cp support-files/mysql.server /etc/init.d/mysql

 

安装权限

sudo chmod 755 /etc/init.d/mysql

 

安装ubuntu运转服务管理

sudo apt-get install sysv-rc-conf 

sudo sysv-rc-conf mysql on

 

将mysql.service变得可用

systemctl enable mysql.service

 

敞开或关闭mysql服务

sudo /etc/init.d/mysql {stop|start}    或者 sudo service mysql start |
stop

 

安排情形变量

sudo vim ~/.bashrc

export PATH=”/usr/local/mysql/bin/:$PATH”

export PATH

 

Author

发表评论

电子邮件地址不会被公开。 必填项已用*标注