When trying to install wxGTK-2.6.1, it reports compiling errors, but the emerge finishes, and the packet installs himself. Reproducible: Always Steps to Reproduce: 1. Issue the "emerge =wxGTK-2.6.1" command. The packet is in testing stage, so you need to unmask it. 2. 3. Actual Results: The compiler errors will be reported and the compilation finishes with the packet installation. Expected Results: When there is a compilation error, the packet shouldn't be installed, and the compilation should fail.
Created attachment 67314 [details] The configure and the compilation results of the packet This file is a explanation of the emerge process.
Created attachment 67315 [details] Errors generated by the build This file contain errors generated by the build
This is normal behavior. They provide the source for all platforms, Windows, Mac, OS/2 etc in one tarball so the ones that don't work on Linux fail. If you find any of the contrib sources fail that affect packages in portage, please re-open.
As a matter of fact, they provide wxGTK version for download, and the wxWindows version for download on the www.wxwidgets.org site. Which archive you are providing through the Portage?
If you look at the ebuild you'll see we don't use the wxGTK tarball (its wxWidgets). The errors affect nothing in any platform we support.
First of all, why you are calling the packet wxGTK? Second you 2 comments are exclusive: first you said: "they provide the sources in one tarball", then you said: "we don't use wxGTK tarball".Which one is correct? Also, when I installed the wxGTK-2.6.1 from the site, everything built normally and my program works as well. So I do think that this is actualy a bug. You need to grab the wxGTK tarball and put it in the portage.
There's no bug here, closing.
