a few additional questions to https://sourceforge.net/tracker/?func=detail&atid=379483&aid=3585712&group_id=23725
What is recommended workflow when deploying applications linked with ATLAS?
Example: Experiment documentation requires source code. Complete ATLAS tarball is not the answer, you can only guess whether you run the same kernel.
Example: Virtual machines are notoriously known to vary performance. ATLAS often refuses to build. You may want to gather more optimization runs.
Example: After initial setup, it is expensive or even impossible to stop all work on the machine to rebuild ATLAS and dependent programs.
Example: Debugging/audit/certification/dumb policy/status report requires builds with and without debuginfo (gcc -g, maybe -O0).
Example: Some free/open source license demands possibility to request source code, patch and rebuild. Hard to satisfy if you do not know, which source corresponds to your current binary. (Not that matrix multiplication is going to get redefined.)
What is the right ATLAS way of doing things?
Thank you very much.