This one has been puzzling me today: I had wxGTK 2.4 already installed, and went to install 2.6 too. Once emerged, I discovered that I couldn't compile applications that required the very same wxGTK 2.6 that I had just installed (one of these was the Catapult frontend from http://openmsx.sourceforge.net/, which is not in portage).
After some research, I discovered that the problem was that the symlink wx-config was still pointing to the 2.4 config script, and that the one for 2.6 was called wx-config-2.6. OK, I could change the symlink making it point to wx-config-2.6, but this seemed a bit hackish for me; actually I thought that something was wrong in the ebuilds.
So I downloaded both source tarballs for wxGTK 2.4 and 2.6, and compiled them in order in my home directory, making them "overlap" on purpose. At the end of this process, it turns out that wx-config is pointing to 2.6 script (as I expected).
Unemerging both 2.4 and 2.6 and reemerging only 2.6 makes wx-config pointing to 2.6 script too (obviously, since there is no 2.4 installed).
Could this be a bug in the ebuild, or somewhere on gentoo's side? Moreover, am I the only one suffering of this problem?


