Package Details: php71-cgi 7.1.33-11

Git Clone URL: https://aur.archlinux.org/php71.git (read-only, click to copy)
Package Base: php71
Description: CGI and FCGI SAPI for php71
Upstream URL: http://www.php.net
Keywords: 7.1 php
Licenses: PHP
Submitter: synthead
Maintainer: wget (el_aur)
Last Packager: el_aur
Votes: 12
Popularity: 0.000000
First Submitted: 2018-03-26 18:04 (UTC)
Last Updated: 2024-03-27 15:00 (UTC)

Dependencies (57)

Required by (0)

Sources (20)

Pinned Comments

el_aur commented on 2022-02-03 18:48 (UTC) (edited on 2022-02-18 10:38 (UTC) by el_aur)

Created binary repository on build.opensuse.org

https://build.opensuse.org/project/show/home:el:archphp

For Arch Linux, edit /etc/pacman.conf and add the following (note that the order of repositories in pacman.conf is important, since pacman always downloads the first found package):

[home_el_archphp_Arch]
Server = https://download.opensuse.org/repositories/home:/el:/archphp/Arch/$arch

Then run the following as root

key=$(curl -fsSL https://download.opensuse.org/repositories/home:el:archphp/Arch/$(uname -m)/home_el_archphp_Arch.key)
fingerprint=$(gpg --quiet --with-colons --import-options show-only --import --fingerprint <<< "${key}" | awk -F: '$1 == "fpr" { print $10 }')
pacman-key --init
pacman-key --add - <<< "${key}"
pacman-key --lsign-key "${fingerprint}"

Refresh packages database

pacman -Syy

Now search for php packages you need:

pacman -Ss php71

Install with pacman -S packages you need or all PHP 7.1 packages with:

sudo pacman -S $(pacman -Ssq | grep '^php71')

el_aur commented on 2022-02-03 18:47 (UTC) (edited on 2022-02-03 18:50 (UTC) by el_aur)

Read Carefully! Breaking changes in compare with native PHP package

  1. Console version /usr/bin/php71 is installed with php71-cli subpackage, php71 doesn't include it anymore!!!

  2. PEAR and PECL are available as php71-pear and php71-pecl subpackages

  3. All shared modules are respresented as stand-alone subpackages and are not included with php71 package anymore.

  4. No more extensions in php.ini itself!

Separate INI files for each extension are placed in /etc/php71/conf.d

They are loaded in correct order according to priority

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 Next › Last »

schlmm commented on 2018-05-23 11:14 (UTC)

Hi,

would be nice if you can add the freetype patch until its fixed upstream

https://bugs.archlinux.org/task/58447 https://bugs.php.net/bug.php?id=76324

thank you

gabrielozaki commented on 2018-04-19 13:57 (UTC) (edited on 2018-04-19 13:58 (UTC) by gabrielozaki)

Hi guys, works for me:

1) remove all php71 packages

2) Install this package(don't worry, this package come with a lot of another packages, like gd,mysql,pgsql...)

3) softlink the module and conf:

ln -s /etc/httpd/modules/php71.so /etc/httpd/modules/libphp7.so

ln -s /etc/httpd/conf/extra/php71_module.conf /etc/httpd/conf/extra/php7_module.conf

4) add this line to <directory "your_webroot_folder"=""> of file /etc/httpd/conf/httpd.conf :</directory>

DirectoryIndex index.php

ncoder-2 commented on 2018-04-10 20:12 (UTC) (edited on 2018-04-10 20:12 (UTC) by ncoder-2)

Wow. Upgraded from php71-7.1.14 to 7.1.16 and it completely broke everything. For some reason libphp7.so changed to php71.so. Then, when manually modifying httpd.conf so apache can start again, php is not reading /etc/php/php.ini and saying the modules are missing etc... Glad I have the pkg/cache to revert...

betarepeating commented on 2018-04-06 23:14 (UTC)

Updated to the latest apache (apache-2.4.33) and suddenly apache would no longer start. I had same error as FrederickZh. Changing the name of the module did not fix it, still got "Can't locate API module structure".

What is my httpd.conf line entry supposed to look like? I changed it to point to the /opt directory but it still did not work.

FrederickZh commented on 2018-04-06 02:56 (UTC) (edited on 2018-04-06 04:11 (UTC) by FrederickZh)

I have both the PHP in the official repo and this one installed and I do prefer having this one in /opt instead of /usr. Installing different versions of a single application all into /usr seems to be a more Ubuntu thing to me actually... I don't have php70 or php56 in my system but I wonder how they maintain the naming consistency as php in official repo never takes multi-version into consideration?

But perhaps we could flatten the directory structure a bit? The /opt/usr tends to be somewhat redundant imo.

Edit: And the naming of php71-apache... Official one is using libphp7.so, so maybe "libphp71.so" is a better choice here?

Edit 2: The apache module is called "php7_module" instead of "php71_module" as shown in php71_module.conf. Using "php71_module" gave me an error of "httpd: Syntax error on line 190 of /etc/httpd/conf/httpd.conf: Can't locate API module structure `php71_module' in file /etc/httpd/modules/php71.so: /etc/httpd/modules/php71.so: undefined symbol: php71_module".

lilmike commented on 2018-04-05 15:22 (UTC)

Patch added to fix intl compilation. Let me know if there are any issues.

synthead commented on 2018-04-04 20:50 (UTC)

@schlmm: I saw where the other packages were configuring and putting their files, and I actually like it a little better in /opt. This naturally keeps the conflicts away without fussing with patches or renaming things (i.e. /etc/php/php.ini, for example). If someone familiar with Linux was told to troubleshoot a problem with an additional PHP 7.1 installation and they saw it in /opt, they'd know exactly what's going on. These are just my personal, subjective thoughts, though. What do you think?

Also, /usr/lib/systemd/system/php71-fpm.service is included in php71-fpm, which is built in this PKGBUILD. Is there something additional you're looking to have included?

@arakmar and @zack6849: I updated the package to build against the latest ICU. Thanks!

@muhviehstarr: Honestly, I don't really like the idea of a /etc/profile.d/ entry because it makes the php binary implicit. With your example, "php" would always refer to the 7.1 binary, even when the upstream php package is installed. This means that other applications that use the php binary without an absolute path would unknowingly execute the 7.1 version. A bit of a gotcha. Instead, I think the right thing to do is to export $PATH or use an absolute path for the specific use cases where PHP 7.1 is necessary. What are your thoughts?

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 Next › Last »