<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hi Everyone,</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>I'm a bit lost on how one should install the Clang <b>pre-built binaries </b>available at <a href="http://llvm.org">llvm.org</a>. I basically have the same questions as someone else has asked on <a href="http://stackoverflow.com/questions/17045954/how-to-install-clang-using-precompiled-binaries">Stack Overflow</a> but want to point out the specific complexity of doing something that requires linking (implicitly) to a clang library. using AddressSanitizer in my case.</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>I'm not totally stuck. I was able to install clang V3.3 using macports. But now I want to get it working on my Ubuntu 12.04 install and am running into the same issue again without macports to rescue me.</div><div><br></div><div><b>On OS X 10.8.3:</b></div><div>I downloaded the pre-built binaries for V3.3 from <a href="http://llvm.org">llvm.org</a>. I don't see any install instructions for this distribution so placed the directory structure in a separate location of my choosing.</div><div>I can compile a simple application with the clang binary. If I compile with -fsanitize=address, still successful. But executing the binary, I got the error: </div><div><br></div><div>"dyld: Library not loaded: /Users/macs/Developer/llvm/final/Phase3/Release-64/llvmCore-3.3-final.obj/Release/lib/clang/3.3/lib/darwin/libclang_rt.asan_osx_dynamic.dylib Referenced from: /Users/me/Downloads/./a.out Reason: image not found Trace/BPT trap: 5".</div><div><br></div><div>Ok, so I tried adding the two lib directories to my DYLD_LIBRARY_PATH environment variable:</div><div>clangV3.3/lib, clangV3.3/lib/clang/3.3/lib/darwin</div><div>With that, I could execute my program and got the expected (wonderful) AddressSanitizer report.</div><div><br></div><div>Was this the right approach? I'm concerned modifying the DYLD_LIBRARY_PATH is going to cause havoc given two Clang installs (the Apple build and this 3.3 build) For instance, there are many more library files in the lib dir than what AddressSanitizer needed.</div><div><br></div><div>Also, the "/Users/macs" path in the error report is not me, but likely the developer who did the build. Seems odd that I see this.</div><div><br></div><div>I suspect that the right answer is that clang/llvm must be configured such that their library search path looks in the right place for the internal libraries. I don't know how to do that, especially after the toolset has been built.</div><div><br></div><div><br></div><div>Thanks for any help that can be provided. Best would be to add documentation to address this matter.</div><div><br></div><div>-Noah</div></body></html>