3 ms·
HPC has the same problem (ancient bespoke Linux distributions with strange tooling) one way to solve it is spack https://github.com/spack/spack https://github.
by orbifold 9y ago
HPC has the same problem (ancient bespoke Linux distributions with strange tooling) one way to solve it is spack https://github.com/spack/spack https://github.com/spack/spack. The ops person where I work is so much in love with it that he tried to get it to work on Mac OS, 2 days later and several patches it took only 8 hours to compile all nescessary transitive dependencies. In my opinion the only good way to solve this is to ignore the distribution package manager and keep track of all dependencies explicitly. Most build systems for C++ make that relatively easy. To choose the compiler / standard library you can then use http://modules.sourceforge.net http://modules.sourceforge.net
- gnufx 9y agoThe RHEL6 compute node image I used to maintain just used rpms (maybe via SCL). I'm inclined to think the trades-off win against Spack and Guix, assuming you don't have the world telling you to use proprietary compilers and libraries that can't be handled that way. The mess I'm used to seeing on HPC systems with combinatorial builds, with everything done through a confusion of environment modules, bothers me and typically confuses users, especially when there's a system package that provides the same thing. (At least look at TACC's Lmod instead of the canonical modules implementation.)