Bug #76560 [Asn->Opn]: Absurd memory allocation during PEAR step of "make install"

Edit report at https://bugs.php.net/bug.php?id=76560&edit=1 ID: 76560 Updated by: cmb@php.net Reported by: php at nearlyfreespeech dot net Summary: Absurd memory allocation during PEAR step of "make install" -Status: Assigned +Status: Open Type: Bug Package: Compile Failure Operating System: FreeBSD PHP Version: 7.3.0beta2 -Assigned To: cmb +Assigned To: Block user comment: N Private report: N New Comment: Thanks for the update! Previous Comments: ------------------------------------------------------------------------ [2018-08-30 01:12:24] php at nearlyfreespeech dot net As of commit 566a75e97c7df74d3172b0b8442d857105123135 to the PHP-7.3 branch (after beta2), this issue is still reproducible with clang, but not with gcc. ------------------------------------------------------------------------ [2018-08-29 21:55:47] cmb@php.net There have been several FreeBSD related fixes lately, so this issue might have been resolved. Or can anybody still reproduce this? ------------------------------------------------------------------------ [2018-07-27 09:14:28] php-bsd1244 at yahoo dot de Hi was able to reproduce the error with FreeBSD 11.2 in conjunction with clang. No issues with gcc indeed. ------------------------------------------------------------------------ [2018-07-20 04:44:54] dc dot link at yahoo dot fr Question out of curiosity, can you build clang from source and try ? Maybe this issue has been solved https://github.com/llvm-mirror/clang/commit/f9af50d37f8d3ae675069543ba14b2a6ace05428 ------------------------------------------------------------------------ [2018-07-19 15:59:35] dc dot link at yahoo dot fr Forget my comment ... confused with Python ... ------------------------------------------------------------------------ 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=76560 -- Edit this bug report at https://bugs.php.net/bug.php?id=76560&edit=1