<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>160197</bug_id>
          
          <creation_ts>2007-01-05 02:03 0000</creation_ts>
          <short_desc>x11-libs/wxGTK : using (almost deprecated) gnuconfig_update</short_desc>
          <delta_ts>2007-01-06 17:10:05 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Eclasses and Profiles</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>All</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          <blocked>160173</blocked>
          
          <everconfirmed>1</everconfirmed>
          <reporter>flameeyes@gentoo.org</reporter>
          <assigned_to>wxwidgets@gentoo.org</assigned_to>
          <cc>vapier@gentoo.org</cc>

      

      
          <long_desc isprivate="0">
            <who>flameeyes@gentoo.org</who>
            <bug_when>2007-01-05 02:03:07 0000</bug_when>
            <thetext>The following ebuilds/eclasses are using the almost deprecated gnuconfig_update function from gnuconfig.eclass:

./x11-libs/wxGTK/wxGTK-2.4.2-r4.ebuild: gnuconfig_update
./x11-libs/wxGTK/wxGTK-2.6.2-r1.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&apos;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 &quot;Waiting autoepatch&quot;.
[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=&quot;..&quot; econf.
[4] Fix your autotools with http://www.gentoo.org/proj/en/qa/autofailure.xml adnd then use econf.

Once you&apos;re using econf, it will take care of updating gnuconfig by itself.

Thanks from Diego and Mike</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>dirtyepic@gentoo.org</who>
            <bug_when>2007-01-06 17:10:05 0000</bug_when>
            <thetext>Fixed.</thetext>
          </long_desc>
      
    </bug>

</bugzilla>