* [Buildroot] [master 1/1] php: disable valgrind
@ 2018-02-12 17:01 Adam Duskett
2018-02-13 21:42 ` Thomas Petazzoni
0 siblings, 1 reply; 2+ messages in thread
From: Adam Duskett @ 2018-02-12 17:01 UTC (permalink / raw)
To: buildroot
Introduced in PHP7.2, if a host has valgrind headers installed, PHP will detect
them and set HAVE_VALGRIND to 1.
Disable this entry after configuring.
fixes:
http://autobuild.buildroot.net/results/d59/d59b5961890aeddcd6d59ed52243be6554d1fe21
Signed-off-by: Adam Duskett <aduskett@gmail.com>
---
package/php/php.mk | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/package/php/php.mk b/package/php/php.mk
index a4481c45c7..e6bc1e47e1 100644
--- a/package/php/php.mk
+++ b/package/php/php.mk
@@ -232,6 +232,11 @@ define PHP_DISABLE_PCRE_JIT
$(SED) '/^#define SUPPORT_JIT/d' $(@D)/ext/pcre/pcrelib/config.h
endef
+define PHP_DISABLE_VALGRIND
+ $(SED) '/^#define HAVE_VALGRIND/d' $(@D)/main/php_config.h
+endef
+PHP_POST_CONFIGURE_HOOKS += PHP_DISABLE_VALGRIND
+
### Use external PCRE if it's available
ifeq ($(BR2_PACKAGE_PCRE),y)
PHP_CONF_OPTS += --with-pcre-regex=$(STAGING_DIR)/usr
--
2.14.3
^ permalink raw reply related [flat|nested] 2+ messages in thread
* [Buildroot] [master 1/1] php: disable valgrind
2018-02-12 17:01 [Buildroot] [master 1/1] php: disable valgrind Adam Duskett
@ 2018-02-13 21:42 ` Thomas Petazzoni
0 siblings, 0 replies; 2+ messages in thread
From: Thomas Petazzoni @ 2018-02-13 21:42 UTC (permalink / raw)
To: buildroot
Hello,
On Mon, 12 Feb 2018 12:01:12 -0500, Adam Duskett wrote:
> Introduced in PHP7.2, if a host has valgrind headers installed, PHP will detect
> them and set HAVE_VALGRIND to 1.
> Disable this entry after configuring.
>
> fixes:
> http://autobuild.buildroot.net/results/d59/d59b5961890aeddcd6d59ed52243be6554d1fe21
>
> Signed-off-by: Adam Duskett <aduskett@gmail.com>
> ---
> package/php/php.mk | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/package/php/php.mk b/package/php/php.mk
> index a4481c45c7..e6bc1e47e1 100644
> --- a/package/php/php.mk
> +++ b/package/php/php.mk
> @@ -232,6 +232,11 @@ define PHP_DISABLE_PCRE_JIT
> $(SED) '/^#define SUPPORT_JIT/d' $(@D)/ext/pcre/pcrelib/config.h
> endef
>
> +define PHP_DISABLE_VALGRIND
> + $(SED) '/^#define HAVE_VALGRIND/d' $(@D)/main/php_config.h
> +endef
> +PHP_POST_CONFIGURE_HOOKS += PHP_DISABLE_VALGRIND
Thanks, applied to master. But when I look at the reason why Valgrind
is incorrectly detected, then I understand why people hate autoconf:
because they don't understand at all how to use it properly, do
completely non-sense utter crap with it, and then complain that
autoconf sucks.
They do this non-sense:
AC_DEFUN([PHP_CHECK_VALGRIND], [
AC_MSG_CHECKING([for valgrind])
SEARCH_PATH="/usr/local /usr"
SEARCH_FOR="/include/valgrind/valgrind.h"
for i in $SEARCH_PATH ; do
if test -r $i/$SEARCH_FOR; then
VALGRIND_DIR=$i
fi
done
if test -z "$VALGRIND_DIR"; then
AC_MSG_RESULT([not found])
else
AC_MSG_RESULT(found in $VALGRIND_DIR)
AC_DEFINE(HAVE_VALGRIND, 1, [ ])
fi
])
Which could be replaced be:
AC_CHECK_HEADERS([valgrind/valgrind.h])
(HAVE_VALGRIND would have to be replaced by HAVE_VALGRIND_VALGRIND_H)
Which has several advantages:
- It is much shorter
- It is not utterly broken for cross-compilation
- It supports a cache variable
If you're in the mood to send a patch to PHP upstream, I think this
would be a useful contribution.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-02-13 21:42 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-02-12 17:01 [Buildroot] [master 1/1] php: disable valgrind Adam Duskett
2018-02-13 21:42 ` Thomas Petazzoni
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox