wxwidgets.eclass gives the user some confusing advice if need-wxwidgets fails. case $1 in wxgtk) echo "!!! You need to emerge wxGTK with wxgtk1 in your USE";; wxgtkd) echo "!!! You need to emerge wxGTK with wxgtk1 in your USE";; gtk-ansi) echo "!!! You need to emerge wxGTK with wxgtk1 in your USE";; gtkd-ansi) echo "!!! You need to emerge wxGTK with wxgtk1 in your USE";; wxgtk2) echo "!!! You need to emerge wxGTK with gtk2 in your USE";; wxgtk2d) echo "!!! You need to emerge wxGTK with gtk2 in your USE";; gtk2-ansi) echo "!!! You need to emerge wxGTK with gtk2 in your USE";; gtk2d-ansi) echo "!!! You need to emerge wxGTK with gtk2 in your USE";; the arguments that don't start with "wx" correspond with wxGTK-2.6, which as of ver 2.6.2 doesn't have gtk2 or wxgtk1 USE flags. all archs except arm currently have at least 2.6.2-r1 stable.
*** Bug 146756 has been marked as a duplicate of this bug. ***
This still spits out confusing messages about non-existant use flags, please fix this.
Fixed, for now. If any ebuilds are doing something stupid like requesting GTK-1 support with WX_GTK_VER=2.6 they'll get this message: !!! GTK-1 support is not available in wxGTK-2.6. !!! Please search bugzilla for this package and file a new bug if one is not already present. But that shouldn't happen since they wouldn't have been able to build anyways. Everything else should give the appropriate action they need to take. We really need to rewrite this eclass.
