The following ebuilds/eclasses are using the almost deprecated gnuconfig_update
function from gnuconfig.eclass:
./app-dicts/dictd-wn/dictd-wn-2.0.ebuild: gnuconfig_update
This might be due by various reasons, and some of them cannot be worked around
at the current time, so please find your case in the following list:
* the ebuild does not use econf, but ./configure, because it uses a very old
version of autoconf that does not support the parameters we pass; [1]
* the software use config.{guess,sub} although not using autotools, thus econf
cannot be used; [1]
* the ebuild uses ./configure just for fun; [2]
* the ebuild uses ../configure or variants thereof to run a different configure
script than the one in the current directory; [3]
* the ebuild uses an autogen script or some other autotools-rebuilding script
that calls ./configure; [4]
* the ebuild calls ./configure because it's doing an inline-build of another
package. [1]
Then see the procedure to handle this bug:
[1] You cannot drop gnuconfig_update, so please leave the bug open, but set the
status whiteboard to "Waiting autoepatch".
[2] Fix the ebuild, use econf!
[3] econf accepts a ECONF_SOURCE variable to tell it to run the configure found
in another directory; to run ../configure just use ECONF_SOURCE=".." econf.
[4] Fix your autotools with http://www.gentoo.org/proj/en/qa/autofailure.xml
adnd then use econf.
Once you're using econf, it will take care of updating gnuconfig by itself.
Thanks from Diego and Mike
