Hello, You're receiving this canned (template-based) bug report because I found an annoyance with a package during my tinderbox run. The package in question is checking for one out of a series of USE flags to be enabled, likely because these are multiple selectable backends, but it currently does not use the EAPI=1 feature of default USE flags to work out of the box. You can see in my blog post in the URL field why that's a problem, and how to address the issue. It would be very kind of you for both users and developers working on automated reporting, if the ebuild for the package enabled by default at least one backend (more might be enabled if needed). Please note that sometimes you don't feel the need for this because the desktop profile already enables some of the USE flags, but please consider the idea of enabling them nonetheless, it would help a lot. Thanks, Diego
In case you mean the die in case USE="-mmx -mmxext" it has been removed, as the code now seems to compile with both disabled. Nevertheless I could not force enable mmx or mmxext, that would be crazy, or not?
Ah sorry I'm behind a few days with the sync :/ You should be able to enable-by-default mmx, user preference in make.conf would override that anyway so if the user knows he has no mmx support and thus set USE=-mmx it would still fail, but the default out-of-tree ebuild would work, on x86/amd64 that is.
Your are not behind, as I checked if it compiles due to this bug, and removed the check just before closing this bug.
