commit:     0e50178a73252a9d0b4445fe82b25ddb663799e2
Author:     Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Wed Sep  2 18:31:58 2015 +0000
Commit:     Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Wed Sep  2 19:34:30 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0e50178a

php-ext-source-r2.eclass: fix WANT_AUTO{CONF,MAKE} warnings.

This is a real fix for the warnings like,

  ac-wrapper: warning: invalid WANT_AUTOCONF 'latest'; ignoring.

reported in bugs #329071 and #549268. In the first of the two, vapier
suggested running $PHPIZE through the autotools_run_tool wrapper, but
this caused builds to fail. In bug #329071, that's where the story
ends.

It turns out, the build failures were due to $PHPIZE containing an
absolute path. Vapier fixed the path handling in autotools.eclass
(commit ecd9954), so now we are able to fix this properly in
php-ext-source-r2.eclass.

Bug: 329071
Bug: 549268

 eclass/php-ext-source-r2.eclass | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/eclass/php-ext-source-r2.eclass b/eclass/php-ext-source-r2.eclass
index ad82fee..de04661 100644
--- a/eclass/php-ext-source-r2.eclass
+++ b/eclass/php-ext-source-r2.eclass
@@ -129,10 +129,10 @@ php-ext-source-r2_src_prepare() {
 # Runs phpize and autotools in addition to the standard src_unpack
 php-ext-source-r2_phpize() {
        if [[ "${PHP_EXT_SKIP_PHPIZE}" != 'yes' ]] ; then
-               # Create configure out of config.m4
-               # I wish I could run this to solve #329071, but I cannot
-               #autotools_run_tool ${PHPIZE}
-               ${PHPIZE}
+               # Create configure out of config.m4. We use autotools_run_tool
+               # to avoid some warnings about WANT_AUTOCONF and
+               # WANT_AUTOMAKE (see bugs #329071 and #549268).
+               autotools_run_tool ${PHPIZE}
                # force run of libtoolize and regeneration of related autotools
                # files (bug 220519)
                rm aclocal.m4

Reply via email to