OK, I think we miss a kind of "blas_switchboard" file that will contain all the info that should not be hardcoded
(try to think more complex scenarios, too, eg. with cuBLAS and such, where some functions are accelerated
and some others are not... but you guys know better how such directions would fit in the easybuild framework)