Compiler une extension PHP
Comment préparer une VM Debian 64 bits pour compiler une extension PHP et compiler simplement une extension ?
Nous allons faire ce tutoriel en se basant sur le code source de YATS, une librairie PHP de templating.
Tout d’abord, ma VM a été créé à partir d’un DVD Debian Server amd64. Les packages choisis lors de l’installation sont “Environnement graphique de bureau” et “Utilitaires standard du système”. La VM est à jour de ses mises à jour de sécurité.
Installons d’abord les paquets :
# apt-get install gcc php5 php5-dev
Testons si PHP fonctionne
$ /usr/bin/php -v
Ensuite, on récupère le code de votre extension… La mienne se situera dans /home/workspace/yats.
On se déplace vers le bon dossier.
$ cd /home/workspace/yats
Pour générer le script configure, on utilise l’outil phpize.
$ phpize Configuring for: PHP Api Version: 20090626 Zend Module Api No: 20090626 Zend Extension Api No: 220090626
On lance le script configure pour génerer le makefile.
$./configure checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for a sed that does not truncate output... /bin/sed checking for cc... cc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ISO C89... none needed checking how to run the C preprocessor... cc -E checking for icc... no checking for suncc... no checking whether cc understands -c and -o together... yes checking for system library directory... lib checking if compiler supports -R... no checking if compiler supports -Wl,-rpath,... yes checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking target system type... x86_64-unknown-linux-gnu checking for PHP prefix... /usr checking for PHP includes... -I/usr/include/php5 -I/usr/include/php5/main -I/usr/include/php5/TSRM -I/usr/include/php5/Zend -I/usr/include/php5/ext -I/usr/include/php5/ext/date/lib checking for PHP extension directory... /usr/lib/php5/20090626 checking for PHP installed headers prefix... /usr/include/php5 checking if debug is enabled... no checking if zts is enabled... no checking for re2c... no configure: WARNING: You will need re2c 0.13.4 or later if you want to regenerate PHP parsers. checking for gawk... no checking for nawk... nawk checking if nawk is broken... no checking --enable-yats... yes, shared checking for a sed that does not truncate output... (cached) /bin/sed checking for fgrep... /bin/grep -F checking for ld used by cc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for ar... ar checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from cc object... ok checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if cc supports -fno-rtti -fno-exceptions... no checking for cc option to produce PIC... -fPIC -DPIC checking if cc PIC flag -fPIC -DPIC works... yes checking if cc static flag -static works... yes checking if cc supports -c -o file.o... yes checking if cc supports -c -o file.o... (cached) yes checking whether the cc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no configure: creating ./config.status config.status: creating config.h config.status: config.h is unchanged config.status: executing libtool commands
Il ne reste plus qu’à compiler
$ make install /bin/bash /home/franklin/workspace/yats/libtool --mode=compile cc -I. -I/home/franklin/workspace/yats -DPHP_ATOM_INC -I/home/franklin/workspace/yats/include -I/home/franklin/workspace/yats/main -I/home/franklin/workspace/yats -I/usr/include/php5 -I/usr/include/php5/main -I/usr/include/php5/TSRM -I/usr/include/php5/Zend -I/usr/include/php5/ext -I/usr/include/php5/ext/date/lib -DHAVE_CONFIG_H -g -O2 -c /home/franklin/workspace/yats/yats.c -o yats.lo libtool: compile: cc -I. -I/home/franklin/workspace/yats -DPHP_ATOM_INC -I/home/franklin/workspace/yats/include -I/home/franklin/workspace/yats/main -I/home/franklin/workspace/yats -I/usr/include/php5 -I/usr/include/php5/main -I/usr/include/php5/TSRM -I/usr/include/php5/Zend -I/usr/include/php5/ext -I/usr/include/php5/ext/date/lib -DHAVE_CONFIG_H -g -O2 -c /home/franklin/workspace/yats/yats.c -fPIC -DPIC -o .libs/yats.o /bin/bash /home/franklin/workspace/yats/libtool --mode=link cc -DPHP_ATOM_INC -I/home/franklin/workspace/yats/include -I/home/franklin/workspace/yats/main -I/home/franklin/workspace/yats -I/usr/include/php5 -I/usr/include/php5/main -I/usr/include/php5/TSRM -I/usr/include/php5/Zend -I/usr/include/php5/ext -I/usr/include/php5/ext/date/lib -DHAVE_CONFIG_H -g -O2 -o yats.la -export-dynamic -avoid-version -prefer-pic -module -rpath /home/franklin/workspace/yats/modules yats.lo libtool: link: cc -shared .libs/yats.o -Wl,-soname -Wl,yats.so -o .libs/yats.so libtool: link: ( cd ".libs" && rm -f "yats.la" && ln -s "../yats.la" "yats.la" ) /bin/bash /home/franklin/workspace/yats/libtool --mode=install cp ./yats.la /home/franklin/workspace/yats/modules libtool: install: cp ./.libs/yats.so /home/franklin/workspace/yats/modules/yats.so libtool: install: cp ./.libs/yats.lai /home/franklin/workspace/yats/modules/yats.la libtool: finish: PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/sbin" ldconfig -n /home/franklin/workspace/yats/modules ---------------------------------------------------------------------- Libraries have been installed in: /home/franklin/workspace/yats/modules If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the `LD_LIBRARY_PATH' environment variable during execution - add LIBDIR to the `LD_RUN_PATH' environment variable during linking - use the `-Wl,-rpath -Wl,LIBDIR' linker flag - have your system administrator add LIBDIR to `/etc/ld.so.conf' See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. ---------------------------------------------------------------------- Installing shared extensions: /usr/lib/php5/20090626/ cp: cannot create regular file `/usr/lib/php5/20090626/#INST@3798#': Permission denied make: *** [install-modules] Erreur 1
Malheureusement, vu que l’on n’est pas administrateur du système, on se connecte en root et on relance la compilation.
$ su - Mot de passe : ******** # cd /home/monextension # make install /bin/bash /home/franklin/workspace/yats/libtool --mode=install cp ./yats.la /home/franklin/workspace/yats/modules libtool: install: cp ./.libs/yats.so /home/franklin/workspace/yats/modules/yats.so libtool: install: cp ./.libs/yats.lai /home/franklin/workspace/yats/modules/yats.la libtool: finish: PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/sbin" ldconfig -n /home/franklin/workspace/yats/modules ---------------------------------------------------------------------- Libraries have been installed in: /home/franklin/workspace/yats/modules If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the `LD_LIBRARY_PATH' environment variable during execution - add LIBDIR to the `LD_RUN_PATH' environment variable during linking - use the `-Wl,-rpath -Wl,LIBDIR' linker flag - have your system administrator add LIBDIR to `/etc/ld.so.conf' See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. ---------------------------------------------------------------------- Installing shared extensions: /usr/lib/php5/20090626/
Et voilà, c’est fait. La compilation est terminée et votre librairie est dans le dossiers des extensions partagées.
Cet article Compiler une extension PHP est apparu en premier sur RootsLabs.