[PATCH] Link against installed library when running lldb test with gcc-4.9.2

Ying Chen chying at google.com
Tue May 26 16:28:01 PDT 2015

Comment at: zorg/buildbot/builders/LLDBBuilder.py:294
@@ -280,1 +293,3 @@
                                  '"lldb all"'])
+            if 'gcc4.9' in compilerPath:
+                testenv=getLibPath(f, compilerPath, env)
vharron wrote:
> Something tells me we should always do this getLibPath or only skip it for gcc4.8
> For example, if we add support for gcc 5.0, we want this.
> Also, does this affect Android builds?  Maybe we should only be adding this lib path on Linux builds?
As suggested by Siva offline, it would be the best if we could somehow set libpath when building the compiler, i.e. the compiler will always go to a particular directory to load libraries. 
I tried --enable-version-specific-runtime-libs and some other flags in configure step of gcc4.9.2, but it doesn't work as expected.
Siva also suggested that we could write script wrapper for gcc4.9.2 to set library path.

Do you know if there's a way to achieve this from host machine rather than during buildbot steps?



More information about the llvm-commits mailing list