<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><span style="font-family:arial,sans-serif">On Mon, Oct 5, 2015 at 9:20 AM, Satish Balay </span><span dir="ltr" style="font-family:arial,sans-serif"><<a href="mailto:balay@mcs.anl.gov" target="_blank">balay@mcs.anl.gov</a>></span><span style="font-family:arial,sans-serif"> wrote:</span><br></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Thanks for the note.<br>
<br>
This sounds more like a 'broken compiler' issue.<br></blockquote><div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">It looks like it when the compiler is invoked from an interpreter (like bash or python). If we run clang from the command line directly, it works fine.</div></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
PETSc buildsystem attempts to not rely on DYLD_LIBRARY_PATH.<br>
<br>
i.e whenever possible - it converts all '-L/foo to '-L/foo<br>
-Wl,-rpath,/foo' in the link line.<br>
<br>
However if 'mpicc/cc' is provided - it assumes it works - and doesn't<br>
try to detect its internal libs - so it won't add -Wl-rpath to such<br>
internal paths - so its likely to fail with mpicc that relies on<br>
DYLD_LIBRARY_PATH<br>
<br>
[Workarround is to add 'LIBS=-Wl,/foo' option to configure]<br>
<br>
I had recently run --download-mpich build [with default compilers] on<br>
'El Capitan' - and that ran fine.<br>
<br>
BTW: is libiomp5.dylib a clang library? [normally I see this with intel compiler]<br></blockquote><div><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Sorry for confusion, the lib name is libomp.dylib. We had to build this library ourselves to enable openmp and then clang version 3.5.x was able to use it (I think we had to use some special branch with older versions of clang). Obviously, we need to change the way we build clang, so it does not rely on DYLD_LIBRAY_PATH and all will be fine.</div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><span style="font-family:arial,sans-serif"> </span></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Also - could you send us the configure.log for a build that breaks with it?<br></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">[so that we can see what exactly breaks on El..]<br></blockquote><div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">It is the typical:</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div>Library not loaded:<br>...<br>Reason: image not found<br></div><div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Log attached.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">--</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">David</div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<span><font color="#888888"><br>
Satish<br>
</font></span><div><div><br>
On Mon, 5 Oct 2015, Andrs, David wrote:<br>
<br>
> Hi guys!<br>
><br>
> If you are not aware of this yet, DYLD_LIBRARY_PATH does not get propagated<br>
> into the child processes on El Capitan. See<br>
> <a href="https://forums.developer.apple.com/message/31148" rel="noreferrer" target="_blank">https://forums.developer.apple.com/message/31148</a><br>
><br>
> I am not sure if that has some implications for your build system, but we<br>
> were not able to build PETSc because one of our libraries (libiomp5.dylib)<br>
> relied on it and the build system failed detecting the compiler (we ship<br>
> our version of clang with MOOSE).<br>
><br>
> I know, it is not a build system issue, it is how we build some underlying<br>
> piece. I just wanted to make you are aware of this.<br>
><br>
> --<br>
> David<br>
><br>
<br>
</div></div></blockquote></div><br></div></div>