Hi Elizabeth,
On 09/02/16 16:55, Elizabeth Fischer wrote:
So... I'm compiling my Python environment with MacPorts, and then
stuff on top of that with EasyBuild. Why MacPorts? Because I just
want it built, and lots of patches are required to compile any other
way. It's one big **** mess.
What kind of problems are you running into exactly when compiling Python
with EasyBuild on OS X?
As you know, OS X isn't our main target, but depending on how much
effort is required, we can try and get the issues fixed, if we know
about them...
Anyway...
I've found that setting (DY)LD_LIBRARY_PATH to include the MacPorts
directory breaks various Python modules. To be specific: it causes
the Mac loader to find dynamic libraries from MacPorts instead of the
/System path. This bug is described here:
https://lists.macosforge.org/pipermail/macports-users/2010-November/022662.html
Well, if you set (DY)LD_LIBRARY_PATH, that's exactly what you want, i.e.
libraries in that location being picked up, no?
I'm compiling my stuff (libraries and Python extensions) with rpath.
So I don't need DYLD_LIBRARY_PATH. The solution, for now, is to run
Python without any DYLD_LIBRARY_PATH.
But this is convincing me that enforcing RPATH on all compiles, as is
done in Spack, should be a high priority for EasyBuild.
We're actively looking into RPATH support, keep an eye on
https://github.com/hpcugent/easybuild-framework/issues/651 (and the
notes of the EasyBuild conf calls).
It's not unlikely it will take a while before we figure things out and
have it stable though...
That being said, RPATH support is something various sites are interested
in, so when we have critical mass and lots of helping hands, it may be
there soon...
regards,
Kenneth
