|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #69657 Shared memory detection during cross-compile fails OPcache
Submitted: 2015-05-18 21:52 UTC Modified: -
From: mhei at heimpold dot de Assigned:
Status: Open Package: *Configuration Issues
PHP Version: 5.6.9 OS: Linux / OpenWrt
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: mhei at heimpold dot de
New email:
PHP Version: OS:


 [2015-05-18 21:52 UTC] mhei at heimpold dot de
At the moment, during the configure stage at compile time, it is determined which shared memory variants are available. For this, tiny C programms are just-in-time compiled and then defines are set.

This does not work well when cross-compiling as we do for OpenWrt for example: we could try to successfully compile the programm, but it is not possible to actually run it.
So without further modification this leads to a php binary/opcache addon which does not have _any_ shared memory implementation compiled in, and it results in errors like this one:

Maybe it possible to not rely the detection on such run-during-compile tests? I'm no autoconf expert, but I wonder whether there is a possibility to "preseed" the test results?
To make it work for OpenWrt, we hacked a patch which simply checks for one important function used by one SHM implementation or the other. But this might not be sufficient.


Add a Patch

Pull Requests

Add a Pull Request

PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Tue May 18 02:01:23 2021 UTC