Bug #66013 [Fbk->Opn]: Solaris build failure

From: Date: Tue, 24 Oct 2017 10:10:34 +0000
Subject: Bug #66013 [Fbk->Opn]: Solaris build failure
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-212263@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=66013&edit=1 ID: 66013 Updated by: cmb@php.net Reported by: Pete_Wall at symantec dot com -Summary: Solaris build failure with 5.5 +Summary: Solaris build failure -Status: Feedback +Status: Open Type: Bug Package: Compile Failure Operating System: Solaris 10 (x86 and SPARC) -PHP Version: 5.5.5 +PHP Version: 7 -Assigned To: cmb +Assigned To: Block user comment: N Private report: N Previous Comments: ------------------------------------------------------------------------ [2017-10-24 04:20:41] g dot fischer at ah-consulting dot net yes, it still happens with php 7. ------------------------------------------------------------------------ [2017-09-21 15:53:24] cmb@php.net Active support for PHP 5 has ended quite a while ago. Does this issue persist with current PHP 7 versions? ------------------------------------------------------------------------ [2016-08-04 05:39:28] norm dot jacobs at oracle dot com FWIW, _XPG4_2 is an internal implementation detail in Solaris and should not be used directly, instead defining _XOPEN_SOURCE >=500 is a possible option. See the standards(5) man page and/or sys/feature_tests.h on Solaris for more detail. ------------------------------------------------------------------------ [2016-07-17 14:58:49] eugene at zhegan dot in Still there in 5.6.21 / Solaris 11.2. ------------------------------------------------------------------------ [2015-07-17 19:02:52] g dot fischer at ah-consulting dot net this is still present in 5.6.11, solaris 11.2, sunpro 5.12. 5.3.x and 5.4.x are fine so it seems it was re-introduced in 5.5.x. also see https://bugs.php.net/bug.php?id=8468 for historical reasons. ------------------------------------------------------------------------ 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=66013 -- Edit this bug report at https://bugs.php.net/bug.php?id=66013&edit=1

« previous php.bugs (#212263) next »