Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 549268 - php-ext-pecl-r2.eclass has depcreated WANT_AUTOCONF="latest" WANT_AUTOMAKE="latest"
Summary: php-ext-pecl-r2.eclass has depcreated WANT_AUTOCONF="latest" WANT_AUTOMAKE="l...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Eclasses (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: PHP Bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-12 13:45 UTC by Sergey S. Starikoff
Modified: 2015-09-02 19:35 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey S. Starikoff 2015-05-12 13:45:30 UTC
Oruginally issue was find on dev-php/pecl-dbase extension (see bug #418353).

emerge dev-php/pecl-ps
…

>>> Emerging (2 of 2) dev-php/pecl-ps-1.3.7::gentoo
 * ps-1.3.7.tgz SHA256 SHA512 WHIRLPOOL size ;-) ...                                                                            [ ok ]
>>> Unpacking source...
…
Configuring for:
PHP Api Version:         20121113
Zend Module Api No:      20121212
Zend Extension Api No:   220121212
ac-wrapper: warning: invalid WANT_AUTOCONF 'latest'; ignoring.
ac-wrapper: warning: invalid WANT_AUTOCONF 'latest'; ignoring.
…

The bug is similiar with previously registered bug #329071
Comment 1 Michael Orlitzky gentoo-dev 2015-08-30 15:02:12 UTC
In bug #329071, vapier suggested using `autotools_run_tool ${PHPIZE}` to fix this. That didn't work -- autotools.eclass tries to dump the output to a file:

  local STDERR_TARGET="${T}/$1.out"

That barfs if we pass an absolute path to autotools_run_tool(). I can make the warning go away by changing our invocation of,

  ${PHPIZE}

to,

  WANT_AUTOCONF="" ${PHPIZE}

Is there a reason why that won't work (other than the fact that it's ugly)?
Comment 2 SpanKY gentoo-dev 2015-09-01 04:49:44 UTC
(In reply to Michael Orlitzky from comment #1)

i think nuking the WANT_xxx vars would prevent people from setting them to specific values in the ebuilds

if the only issue is the logging path, we could just use ${1##*/}.out as the file name.
Comment 3 Michael Orlitzky gentoo-dev 2015-09-01 11:30:58 UTC
(In reply to SpanKY from comment #2)
> (In reply to Michael Orlitzky from comment #1)
> 
> if the only issue is the logging path, we could just use ${1##*/}.out as the
> file name.

That works for us if it doesn't cause any other problems.


> i think nuking the WANT_xxx vars would prevent people from setting them to
> specific values in the ebuilds
> 

Ah, I guess I could wrap it in a test then, if WANT_FOO = "latest"...
Comment 4 SpanKY gentoo-dev 2015-09-02 04:50:51 UTC
(In reply to Michael Orlitzky from comment #3)

should be all set then:
http://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ecd9954d249956d09be0f4803b1b8766ae203adc
Comment 5 Michael Orlitzky gentoo-dev 2015-09-02 19:35:51 UTC
(In reply to SpanKY from comment #4)
> (In reply to Michael Orlitzky from comment #3)
> 
> should be all set then:
> http://gitweb.gentoo.org/repo/gentoo.git/commit/
> ?id=ecd9954d249956d09be0f4803b1b8766ae203adc

Thanks! The PECL eclass is fixed in,

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0e50178a73252a9d0b4445fe82b25ddb663799e2