As per summary. Triggers things like this ac-wrapper: warning: invalid WANT_AUTOCONF 'latest'; ignoring. ac-wrapper: warning: invalid WANT_AUTOCONF 'latest'; ignoring. during emerge of e.g. dev-php5/pecl-yaz. Reproducible: Always
This is a general error. It's not specific to this eclass. Here's what i put together: (1) the eclass inherits autotools.eclass (2) autotools.eclass exports WANT_AUTOCONF with the value taken from the environment, defaulting to "latest" if not set (3) php-ext-source-r1.eclass calls phpize, which in turn calls ac-wrapper to update the php extension sources (4) ac-wrapper outputs the messages you reported @base-system: you maintain autotools.eclass - can you advise on how to solve this?
Just remove WANT_AUTOCONF="latest" WANT_AUTOMAKE="latest" from the eclass, and profit?
I did. autotools.eclass sets those as defaults, then exports them. At least, that's what I figured from line 20ff of it.
if you arent using the e* helpers from autotools.eclass and instead are executing autotools directly, why are you inheriting autotools.eclass ?
After running phpize (which calls ac-wrapper directly), the eclass runs eautoreconf. phpize is external to the eclass and installed along with php. Maybe I can patch it, but a generic solution might be more effective?
what if you ran phpize differently. like so: (PHP_AUTOCONF=eautoconf; PHP_AUTOHEADER=eautoheader; . ${PHPIZE}) || die your other option might be to do something like: autotools_run_tool ${PHPIZE}
I will need to revisit that, but for now i fixed it with autotools_run_tool phpize ${PHPIZE} expands to the full path and kills the build process. I couldn't figure out why. For the moment, /usr/bin/phpize is a link to our (only) copy of phpize in /usr/$(get_libdir)/php5/bin/phpize This may change once we introduce minor version slotting into the mix and there'll be multiple phpizes once again.
Well the issue resurfaced with php-ext-source-r2.eclass @vapier: I tried your other fix, but braindead phpize does test -x on the PHP_AUTOCONF you're passing it. Having no eautoconf binary ready kills the process. I figured I /can/ run ${PHPIZE} (the full path version) if I mkdir the path before calling autotools_run_tool, but I'd rather avoid that.
Should be fixed by mabi in php-5.3.5-r1
