Created attachment 671668 [details] dev-libs/icu[abi_x86_32] build log (gzip). Hello, dev-libs/icu[abi_x86_32] fails to emerge with the following message: > The futex facility returned an unexpected error code. It turns out it fails if kernel is not compiled with its option `CONFIG_COMPAT_32BIT_TIME` set. Activating this option and reemerging this package made it works. Related to bug 733414. Please see the attached log of the failed build. Steps to reproduce, always reproducible: 1. Run a kernel without `CONFIG_COMPAT_32BIT_TIME` option; 2. Emerge dev-libs/icu with abi_x86_32 support. So, I was thinking it could be a good help for other people with this specific setup to either display a warning message at the start to compilation or even (if possible) blocks Portage before starting to emerge package until this dependency inside the kernel itself is satisfied. I was thinking about a third approach too, see if the test is relevant (the execution of ../bin/icupkg), and if not, maybe ignoring it (or just displaying a warning) instead of failing the compilation. This bug is therefore a minor one, it’s here just a question about improving support for x86_32 programs when the `CONFIG_COMPAT_32BIT_TIME` kernel option is deactivated. Thanks for your attention.
this bug also in (app-crypt/heimdal-7.7.0-r2) package. Information about the problem is not yet listed here.
Ouch, i'm updating an old x86 (32bit) gentoo, and was hit by this. Several stuff won't start with an error "The futex facility returned an unexpected error code.", such as syslog-ng or openssh. Adding CONFIG_COMPAT_32BIT_TIME to the kernel did fix it, indeed. Definitely worth adding somewhere in the doc imho.
