diff options
| author | Michael Heimpold <mhei@heimpold.de> | 2018-02-14 14:46:17 +0100 |
|---|---|---|
| committer | Nikita Popov <nikita.ppv@gmail.com> | 2018-03-23 22:02:17 +0100 |
| commit | 25ba60b1479eb332a7388732f3ee5467000fbe73 (patch) | |
| tree | 4165081af39e479de22d2e7e64b75f3174861c9d /ext/xml/php_xml.h | |
| parent | 7f4327bc244263818bb12d4dc87f8a454e0392f2 (diff) | |
| download | php-git-25ba60b1479eb332a7388732f3ee5467000fbe73.tar.gz | |
Fixed bug #75722: Rework valgrind detection
As described in bug report #75722, the configure script (acinclude.m4)
currently searches for the valgrind header file and enables valgrind
support if found.
When cross-compiling the searched paths are invalid for the target
platform because they belong to the host system. At the moment, there is
no way to tell the build system a dedicated path where to look for the
header file.
This leads to the issue, that when cross-compiling eg. for ARMv5 platform,
that valgrind header file is detected - e.g. because host system is amd64 -
and support is enabled - but target platform will never support valgrind
(valgrind requires e.g. at least ARMv7).
This change reworks the detection so that user could manually opt-in
valgrind support and optionally specify a directory where the build system
should look for the header file using the --with-valgrind option.
Diffstat (limited to 'ext/xml/php_xml.h')
0 files changed, 0 insertions, 0 deletions