The --enable-everything option specifically enables most of the options that are then re-enabled with --enable-foo in the econf call. Purely cosmetic, but in this instance it helps to understand what is actually being enabled in my opinion. Without having to check both --enable-everything's rule and also --enable-foo's rule and check they don't clash. The only exception is the --enable-shared, which I think I must be missing the point of. According to the ebuild and package, as far as I can tell, it is doing absolutely nothing at all. Any pointers about the reason for linguas_* usage would be greatly appreciated too. Where are they defined? And for what its worth some of the options their tests set are enabled by default too. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 56410 [details, diff] mrxvt-enable_everyting_cleanup.patch
k, I cleaned --enable-* flags from the ebuild (it was copied from x11-terms/rxvt and I can't remember why they were there). linguas_* USE flags are defined by USE_EXPAND. See /etc/make.globals for default USE_EXPAND. linguas_* are our de facto USE flags for multilingual support. I don't think it's good but anyway we are using them :( If you are interested in m17n support in portage-wise, have a look at bug #9988.
Thanks for the resolution, and answering my clueless questions too.
