Created attachment 400810 [details] build.log Build fails because I have -mno-ssse3 in CFLAGS (since it is broken on x86(_32) Haswell).
Clarification: It is SSSE3 that is broken, not the -mno-ssse3 CFLAG :)
Yeah, it's due to automagic support_aesni cabal flag enabled in ebuild. Fixing.
Pushed as: > 09 Apr 2015; Sergei Trofimovich <slyfox@gentoo.org> cipher-aes-0.2.10.ebuild, > metadata.xml: > Guarded -maesni under CPU_FLAGS_X86=aes (bug #545926 by Luke-Jr). Thanks!
(In reply to Sergei Trofimovich from comment #3) > Pushed as: > > > 09 Apr 2015; Sergei Trofimovich <slyfox@gentoo.org> cipher-aes-0.2.10.ebuild, > > metadata.xml: > > Guarded -maesni under CPU_FLAGS_X86=aes (bug #545926 by Luke-Jr). > > Thanks! This doesn't really fix it: AES works fine on my CPU, just not SSSE3... Maybe add REQUIRED_USE="cpu_flags_x86_aes? ( cpu_flags_x86_ssse3 )"?
Created attachment 400894 [details, diff] patch for ebuild This uses both CPU_FLAGS_X86 flags and requires them both or neither.
> This doesn't really fix it: AES works fine on my CPU, just not SSSE3... > Maybe add REQUIRED_USE="cpu_flags_x86_aes? ( cpu_flags_x86_ssse3 )"? Oh, I've mixed it with SSE3 :) Thanks for the fix! Pushed fix as: > 09 Apr 2015; Sergei Trofimovich <slyfox@gentoo.org> cipher-aes-0.2.10.ebuild, > metadata.xml: > Enable AES-NI only when both AES-NI and sSSE3 are present. Bug #545926 and fix > by Luke-Jr. I didn't use REQUIRED_USE as it's quite annoying for users to micromanage these binary things with 4 states of flags. .ebuild will enable gcc's intrisics only when both flags are enabled otherwise it will be silently disabled.