dev-perl/wxperl-0.56 depends on dev-perl/Alien-wxWidgets-0.19 which also depends on dev-perl/Module-Pluggable-3.1-r1. Both are missing ~ia64, thus removing ~ia64 from dev-perl/wxperl-0.56. Could you please keyword these two ebuilds and then re-keyword dev-perl/wxperl-0.56? Thanks :)
wxperl-0.5[67] look pretty screwed to me. They DEPEND on >=x11-libs/wxGTK-2.6.2-r1 but they're hardcoded to build with -I/usr/lib/wx/include/gtk2u-2.4 with apparently no concept of wx-config at all. However if the ebuilds are modified (see patch) then they don't build because they depend on wx/arrstr.h which only comes with wxGTK-2.6.x Any suggestions?
Created attachment 99701 [details, diff] patch to build wxperl with wxGTK-2.4
Please try to make it work with 2.6 and keep the DEPEND on that. I really want to get rid of 2.4 ASAP... wxperl homepage seems to indicate that it should work with 2.6, and even some preliminary 2.7 work seems to have been done
No, we don't try to compile with 2.4 (you've went over the ebuild, you should've noticed :)). agriffis, do you have both 2.4 AND 2.6 installed? leio, it was tested with 2.6 and works. (Actually, it won't work and shouldn't be compiled with 2.4) If there's a problem, please file a bug.
There might be issues when wx-config symlink points to wx-config-2.4, which it does if the system has both wxGTK versions installed. The wxwidgets eclass sets environment variables WX_CONFIG, WX_CONFIG_NAME, WXBASE_CONFIG_NAME which are then picked up by configure based build systems that properly use wxwin.m4 aclocal macros to handle wx versioning - see /usr/share/aclocal/wxwin.m4 -> AM_PATH_WXCONFIG explanation in comments. WX_CONFIG_NAME is the one that is used in 2.6's wxwin.m4 and others might be redundant, but I'd need to check 2.4's wxwin.m4 to be sure. With the current collision-protect violating mess with 2.4 and 2.6 it might happen that a system has wxwin.m4 from 2.4 installed. Once 2.4 is out the tree and I start looking at adding 2.8 (or 2.7 in p.mask) I will fix this mess with an eselect module or whatnot - however the build procedure will still have to obey WX_CONFIG_NAME or different means (that would have to be added to the eclass) for selecting the wx-config to use, as wx-config will be a means for users to select which version they want to use for self-compiled packages, while the portage provided packages need to go through the eclass and the WX_GTK_VER in the packages ebuild. I believe the magic in build/Wx/build/MakeMaker* doesn't honor WX_CONFIG_NAME and always just picks /usr/bin/wx-config, which will then get the configuration that agriffis got (2.4).
I opened bug 151417 for the issue described in comment #5. agriffis: You should be able get around the issue meanwhile by adjusting the /usr/bin/wx-config symlink by hand to point to /usr/bin/wx-config-2.6 or /usr/lib/wx/config/gtk2-unicode-debug-2.6 (or appropriate settings in /usr/lib/wx/config - probably release instead of debug, etc). A wxGTK installation on a system without wxGTK-2.4* points it to /usr/lib/wx/config/gtk*
What's the status of this? agriffis is retired, so if you think it's okay if it works with wxGTK-2.6 i'll add the keywords. I'm saying so since wxGTK-2.4 is going to be removed...
~ia64 done, closing.
