wxwidgets.eclass use the old fashion "set-wxconfig" tool and report the error : Compile wxGTK with unicode USE flag. But This error doesn't correspond to the real problem. Reproducible: Always Actual Results: When emerging pgadmin3, the ebuild call "need-wxwidgets unicode". This fail in error with a bad error message. Expected Results: Compile and run
Created attachment 118990 [details] Set-wxconfig replaced by wx-config New proposal for wxwidgets.eclass
Not portage.
Also, please attach a unified diff, instead of the whole eclass.
Created attachment 118991 [details, diff] Diff file to patch the current wxwidgets.class Diff file to patch the current wxwidgets.class
Comment on attachment 118991 [details, diff] Diff file to patch the current wxwidgets.class In fact, the problem come from wxGTK which is the 2.8 version
This is needed to be able to use wxGTK 2.8
Created attachment 119000 [details, diff] Patch fo supported wxGTK 2.8 A more serious one
thanks, but we have a completely rewritten eclass we're in the process of testing right now. it'll be ready for the public pretty soon, so stay tuned.
Ok thx
The premise of this patch is unfortunately completely wrong anyway. There is nothing old in set-wxconfig - it is a bash function inside the very same eclass. wx-config is a configuration utility which we can NOT use inside portage installations as it is heavily dependent on which SLOT was last installed and so on. It also does not accept things like gtk-ansi as an argument (well it does, but spits out nonsense for the lib names then). Thanks for the concern though and I hope this information helps for future patches from you in this area after the rework is in :) Marking bug as closed.
