Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 203298 - unknown function _wxerror in wxwidgets.eclass
Summary: unknown function _wxerror in wxwidgets.eclass
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Eclasses (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo wxWidgets project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-25 14:18 UTC by Fabio Rossi
Modified: 2007-12-25 16:32 UTC (History)
0 users

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 Fabio Rossi 2007-12-25 14:18:10 UTC
The wxwidgets.eclass contains an unknown function, _wxerror, at line 230
Comment 1 Mart Raudsepp gentoo-dev 2007-12-25 14:35:51 UTC
I think this error is only hit if the ebuild doesn'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?
Comment 2 Mart Raudsepp gentoo-dev 2007-12-25 14:49:33 UTC
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'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 "unknown function" :)
Comment 3 Fabio Rossi 2007-12-25 15:30:15 UTC
(In reply to comment #2)
> Fabio, you were probably hitting a check_wxuse call inside an ebuild that
> doesn'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 "unknown function" :)

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:

>>> 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 'pkg_setup'
 *                 ebuild.sh, line   44:  Called pkg_setup
 *   wxpython-2.6.4.0.ebuild, line   36:  Called check_wxuse 'opengl'
 *          wxwidgets.eclass, line  234:  Called built_with_use '=x11-libs/wxGTK-*' 'opengl'
 *             eutils.eclass, line 1664:  Called die
 * The specific snippet of code:
 *      [[ -z ${PKG} ]] && die "Unable to resolve $1 to an installed package"
 *  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 '/var/log/portage/dev-python:wxpython-2.6.4.0:20071225-124117.log'.
 *
 * GNU info directory index is up-to-date.
Comment 4 Ryan Hill (RETIRED) gentoo-dev 2007-12-25 16:32:11 UTC
yep, looks like the correct fix.  brain damage on my part.

fixed wxpython.2.6.4.0 as well.