On Tuesday, 07 October 2014, at 12:57:00 (-0700), Jeff Squyres (jsquyres) wrote:
> > However, autotools by default use <prefix>/lib, not > > <prefix>/lib<arch>, so I suspect that's where the "conflict" arises. > > Still seems weird -- can't SLURM's configure compensate for this, when it > detects that the perl installation dir != $libdir? Especially when SLURM is > installed into an empty tree (vs., say, / or /usr). I would say that step 1 is making sure we've successfully identified the culprit. :-) Multiple possible solutions are available, depending on what users' expectations are and how Moe & Danny want things to be orchestrated by default. I would say further discussion should ensue if Timothy confirms that we have indeed pinpointed what's going on and that --libdir "fixes" the issue. Is this a problem because OpenMPI uses the existence of the <prefix>/lib64 directory as a litmus test for something? I'm wondering why this particular scenario would adversely affect the OpenMPI code or build process. If you (or Timothy) wouldn't mind elaborating on the specific problem being encountered, that might be helpful! :-) Michael -- Michael Jennings <[email protected]> Senior HPC Systems Engineer High-Performance Computing Services Lawrence Berkeley National Laboratory Bldg 50B-3209E W: 510-495-2687 MS 050B-3209 F: 510-486-8615
