diff options
authorSam James <>2022-01-17 02:58:42 +0000
committerSam James <>2022-01-17 02:58:42 +0000
commit7ce5b6fde46ba698919feec73ccee5bdaaf4f8c6 (patch)
treea5727b42ab0a4398fc793aaf64401e9784f3059e /sys-kernel/genkernel/genkernel-4.0.5.ebuild
parentdev-libs/libgcrypt: add cpu_flags_ppc_vsx2 (diff)
dev-libs/libgcrypt: wire up CPU_FLAGS_ARM_* for crypto extensionsHEADmaster
Note that we currently use an all-or-nothing approach as I'm only aware of ARM CPUs supporting all of: cpu_flags_arm_{aes,sha1,sha2} or none, but it does look like it's possible (or will be in future) to support some crypto extensions but not all. The libgcrypt build system only exposes --disable-arm-crypto-support which uses at least both AES and SHA* instructions right now with no way to disable just one. Given in the wild, we're only aware of all-or-nothing CPUs, let's just add REQUIRED_USE logic for safety for now, and enable/disable based on all of cpu_flags_arm_{aes,sha1,sha2} being set by the user (which, again, should be the case for all known CPUs. cpuid2cpuflags will do this automatically.) Needed to avoid automagic usage of crypto extensions which may cause problems for e.g. binpkgs. Signed-off-by: Sam James <>
Diffstat (limited to 'sys-kernel/genkernel/genkernel-4.0.5.ebuild')
0 files changed, 0 insertions, 0 deletions