On Tuesday, 14 October 2014, at 10:58:53 (-0700), Jeff Squyres (jsquyres) wrote:
> Yes, it can (and has) led to broken scenarios for users (confusion > about mixing 32 and 64 bit libraries in the same build). Understood. > Agreed; it wouldn't be good to assume this. But it should be easy > enough to check and see if libtool is going to install into one > place and perl is going to install into another. And if that's the > case, perhaps configure should error out. > > ... > > Yes. Or perhaps configure could just error out if it detects a > mismatch (and therefore let a human figure out, perhaps by supplying > --libdir to override lib tool's default install location, etc., or > passing PERLARCHLIB=...). I agree with you. As for what the right answer is, hopefully Moe or Danny will chime in at this point. Or someone from SchedMD. It's an administrative choice as to which is the right way to go. I think most folks would expect PERLARCHLIB to correlate with $libdir (and $prefix/lib*) when using a custom prefix; I think it's quite reasonable to take specific actions when --prefix is given (outside of /usr and /usr/local) that aren't taken otherwise. But as I said before, I don't have the BG/Cray experience to say what those systems' expectations or caveats are. :-) 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
