Package Base Details: php71

Git Clone URL: (read-only, click to copy)
Keywords: 7.1 php
Submitter: Synthead
Maintainer: wget
Last Packager: wget
Votes: 10
Popularity: 0.000006
First Submitted: 2018-03-26 18:04
Last Updated: 2019-11-03 19:03

Pinned Comments

wget commented on 2019-02-11 11:49

This package makes use of GPG keys for integrity verification. Here are the PGP keys you need to import (if you trust them):

$ gpg --recv-keys A917B1ECDA84AEC2B568FED6F50ABC807BD5DCD0 528995BFEDFBA7191D46839EF9BA0ADA31CBD89E 1729F83938DA44E27BA0F4D3DBDB397470D12172

Receiving GPG keys might fail with the following error message: $ gpg: keyserver receive failed: Connection refused. If this happens, just check your DNS or use other ones.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

Synthead commented on 2018-04-04 20:50

@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?

zack6849 commented on 2018-04-04 20:05

Doesn't build properly for me, get compiler errors, is this package still maintained?

lilmike commented on 2018-04-03 13:29

Unfortunately that seems to be a conflict between php and the new version of the required library on arch. I've opened a bug on, and will definitely update the package with any patches as I receive them. Just hold tight!


XenGi commented on 2018-04-03 13:20

The new update to 7.1.16 doesn't compile anymore. Here's the output:

Some UnicodeError and other stuff.

muhviehstarr commented on 2018-04-02 16:45

maybe you should add bin links or add /opt/php71/usr/bin to PATH via an /etc/profile.d/ entry like this:



export PATH=$PATH:/opt/php71/usr/bin

this will avoid fail updates like nextcloud which use the php binary for updates for users that only have installed php71

arakmar commented on 2018-03-30 08:05

Hi, A build fix since the latest icu update :

schlmm commented on 2018-03-28 15:30

also a systemd service would be nice thx

schlmm commented on 2018-03-28 15:29

could you rewrite it so the files are under /usr like in php70 and php56 package? would be nice

Synthead commented on 2018-03-26 18:22

This package puts PHP 7.1 in /opt/php71, so it can be installed alongside the php package in the mirrors. I have also uploaded uwsgi-plugin-php71, php71-apcu, and php71-apcu-bc, which is enough to get ZoneMinder (and the API) working without issues.

snike commented on 2018-03-23 03:36

Knowing the source and having checked the integrity manually, I went with

makepkg --skipinteg

Thanks for maintaining this package