<?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>203298</bug_id>
          
          <creation_ts>2007-12-25 14:18 0000</creation_ts>
          <short_desc>unknown function _wxerror in wxwidgets.eclass</short_desc>
          <delta_ts>2007-12-25 16:32:11 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>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>rossi.f@inwind.it</reporter>
          <assigned_to>wxwidgets@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>rossi.f@inwind.it</who>
            <bug_when>2007-12-25 14:18:10 0000</bug_when>
            <thetext>The wxwidgets.eclass contains an unknown function, _wxerror, at line 230</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>leio@gentoo.org</who>
            <bug_when>2007-12-25 14:35:51 0000</bug_when>
            <thetext>I think this error is only hit if the ebuild doesn&apos;t properly set WX_GTK_VER before calling need-wxwidgets or check_wxuse, that is, the call to an unknown function is inside that error codepath.
I think we can just change it to eerror, but I recall seeing the _wxerror function somewhere doing something. dirtyepic, is this just a thinko from the _wxerror in wx-config wrapper?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>leio@gentoo.org</who>
            <bug_when>2007-12-25 14:49:33 0000</bug_when>
            <thetext>For now fixed the check for WX_GTK_VER to be the same in check_wxuse as it already was in need-wxwidgets, using eerror + die instead of that not existing _wxerror. Ryan (dirtyepic), feel free to revise that of course.

Fabio, you were probably hitting a check_wxuse call inside an ebuild that doesn&apos;t set WX_GTK_VER anywhere (in global scope or in the function) before calling that. Curious what ebuild is that? Might need a fix, as now it will just error with better description than &quot;unknown function&quot; :)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>rossi.f@inwind.it</who>
            <bug_when>2007-12-25 15:30:15 0000</bug_when>
            <thetext>(In reply to comment #2)
&gt; Fabio, you were probably hitting a check_wxuse call inside an ebuild that
&gt; doesn&apos;t set WX_GTK_VER anywhere (in global scope or in the function) before
&gt; calling that. Curious what ebuild is that? Might need a fix, as now it will
&gt; just error with better description than &quot;unknown function&quot; :)

I found the problem (WX_GTK_VER unset) when I was trying to emerge wxpython-2.6.4.0. I solved unmasking wxpython-2.6.4.0-r1 :-)

Here is the error log:

&gt;&gt;&gt; Emerging (2 of 4) dev-python/wxpython-2.6.4.0 to /
 * wxPython-src-2.6.4.0.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                                                                                      [ ok ]
 * checking ebuild checksums ;-) ...                                                                                                                 [ ok ]
 * checking auxfile checksums ;-) ...                                                                                                                [ ok ]
 * checking miscfile checksums ;-) ...                                                                                                               [ ok ]
 * checking wxPython-src-2.6.4.0.tar.bz2 ;-) ...                                                                                                     [ ok ]
 * Determine new optimal TMPFS value: [ 1969M ]
 * Mounting /var/tmp/portage/dev-python/wxpython-2.6.4.0 of [ 1969M ] ...                                                                            [ ok ]

/usr/portage/eclass/wxwidgets.eclass: line 230: _wxerror: command not found
 * Checking wxGTK- for opengl support ...
 *
 * ERROR: dev-python/wxpython-2.6.4.0 failed.
 * Call stack:
 *                 ebuild.sh, line 1717:  Called dyn_setup
 *                 ebuild.sh, line  768:  Called qa_call &apos;pkg_setup&apos;
 *                 ebuild.sh, line   44:  Called pkg_setup
 *   wxpython-2.6.4.0.ebuild, line   36:  Called check_wxuse &apos;opengl&apos;
 *          wxwidgets.eclass, line  234:  Called built_with_use &apos;=x11-libs/wxGTK-*&apos; &apos;opengl&apos;
 *             eutils.eclass, line 1664:  Called die
 * The specific snippet of code:
 *      [[ -z ${PKG} ]] &amp;&amp; die &quot;Unable to resolve $1 to an installed package&quot;
 *  The die message:
 *   Unable to resolve =x11-libs/wxGTK-* to an installed package
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at &apos;/var/log/portage/dev-python:wxpython-2.6.4.0:20071225-124117.log&apos;.
 *
 * GNU info directory index is up-to-date.
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>dirtyepic@gentoo.org</who>
            <bug_when>2007-12-25 16:32:11 0000</bug_when>
            <thetext>yep, looks like the correct fix.  brain damage on my part.

fixed wxpython.2.6.4.0 as well.</thetext>
          </long_desc>
      
    </bug>

</bugzilla>