Edit report at https://bugs.php.net/bug.php?id=76826&edit=1
ID: 76826
Patch added by: ab@php.net
Reported by: php-bugs-2018 at ryandesign dot com
Summary: error: use of undeclared identifier 'finite'
Status: Open
Type: Bug
Package: Compile Failure
Operating System: Mac OS X 10.7.5
PHP Version: 7.2.9
Block user comment: N
Private report: N
New Comment:
The following patch has been added/updated:
Patch Name: bug76826.poc.0.patch
Revision: 1538723399
URL: https://bugs.php.net/patch-display.php?bug=76826&patch=bug76826.poc.0.patch&revision=1538723399
Previous Comments:
------------------------------------------------------------------------
[2018-10-05 02:35:46] php-bugs-2018 at ryandesign dot com
Yes, we know Mac OS X 10.7 is old. But maybe there's somebody out there trying to learn PHP,
and the only computer they have available is an old hand-me-down Mac that cannot be upgraded past
10.7.
Here are some fresh build logs for you, on Mac OS X 10.7.5, Xcode 4.6.3, Apple LLVM version 4.2
(clang-425.0.28) (based on LLVM 3.2svn).
php 7.1.22: https://build.macports.org/builders/ports-10.7_x86_64_legacy-builder/builds/78701/steps/install-port/logs/stdio
php 7.2.10: https://build.macports.org/builders/ports-10.7_x86_64_legacy-builder/builds/78702/steps/install-port/logs/stdio
Can't provide a build log of php 7.3.x because of bug #76825.
------------------------------------------------------------------------
[2018-10-04 20:27:30] ab@php.net
@elis the build log seems to available anymore. Perhaps a gist could work? Also the OS and compiler
version were interesting to know.
@php-bugs-2018 Otherwise I was doing some research and stumbled upon the fact, that OS X 10.7 is EOL
already for about 4 years. It seems that even 10.9 already EOL. The issue seems quite weird because
the condition https://github.com/php/php-src/blob/master/configure.ac#L85
checks already whether it's lower than C++11. You could try to remove __cplusplus check in
configure.ac and Zend/configure.ac and see whether it changes something. If it doesn't, that it
is probably missing the other part of the condition.
Thanks.
------------------------------------------------------------------------
[2018-09-17 09:51:22] elis at hirwing dot se
In Nix we have the same issue when building our packages on darwin.
It's present in 7.2.9, 7.2.10 as well as 7.1.21. It's not present in 7.0.32 or 5.6.38.
Here's a full build log of 7.2.10 on Darwin: https://logs.nix.ci/?key=nixos/nixpkgs.46694&attempt_id=f33785ed-b114-4eee-82b6-83fe93439e25
For the moment we have disabled the intl module on Darwin just to get the new versions into our
unstables. But since we changed the feature set available it also means that we're unable to
backport bug fix releases to our users of our stable channels on both NixOS, other Linux and Darwin.
------------------------------------------------------------------------
[2018-09-03 13:08:57] php-bugs-2018 at ryandesign dot com
I do use phpize from the same version of PHP. I know that intl can be built as a separate extension
using phpize; we do so in MacPorts. This bug report is that on this specific version of Mac OS X
with its version of Xcode, and this version of PHP, it fails to compile. It's not a problem
with older versions of PHP on this version of Mac OS X and Xcode, and it's not a problem with
this version of PHP on other versions of Mac OS X and Xcode.
Both on Mac OS X 10.7 where the build fails, and on 10.8 and later up to at least 10.13 where the
build succeeds, __cplusplus is 199711L. On Mac OS X 10.6 where the build also succeeds, the Apple
gcc 4.2.1 compiler is used, and its __cplusplus value is 1.
------------------------------------------------------------------------
[2018-09-03 12:53:36] ab@php.net
Thanks for the report. Perhaps you need to use phpize from the same (or at least) PHP version. Older
PHP versions will have different php_config.h. Otherwise, ext/intl can also be built shared.
Btw, what does __cplusplus macro contain?
Thanks.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=76826
--
Edit this bug report at https://bugs.php.net/bug.php?id=76826&edit=1