Use module-only when a CUDA Compute Capability is requested that is incompatible with the CUDA toolkit version used#146

Open

casparvl wants to merge 9 commits intoEESSI:mainfrom

casparvl:CUDA_cuDNN_hooks_202506

Commits on Dec 24, 2025

Add some initial changes to the hooks to make sure to install with --module-only if this is CUDA-12.6 based but targets CC100 or CC120
Caspar van Leeuwen
committed

Commits on Jan 7, 2026

Make mechanism to generate modules that print LmodErrors for unsupported configurations more generic. Then, also apply this to unsupported combinations of CUDA toolkit versions and requested CUDA c…
Caspar van Leeuwen
committed
Remove some variables that have become obsolete, and make sure get_cuda_version actually returns 'None' if CUDA was not in the deps
Caspar van Leeuwen
committed
Remove the now obsolete zen4 parse hook - we now inject the lmodfooter in the pre-module hook
Caspar van Leeuwen
committed
Remove zen4-specific pre and post prepare hooks, as these were replaced by the generic X_prepare_hook_unsupported_modules
Caspar van Leeuwen
committed
Remove the prepare_hooks that were specific to zen4, as they were replaced by generic hooks
Caspar van Leeuwen
committed

Commits on Jan 8, 2026

Actually implement is_cuda_cc_supported_by_toolkit. Also, make sure environment variables don't contain invalid characters like commas and periods. Add some warning messages if installing a module …
Caspar van Leeuwen
committed
Move import to the top
Caspar van Leeuwen
committed
Fix description for 'is_supported_module' as it no longer returns an environment name
Caspar van Leeuwen
committed