Page MenuHomePhabricator

Link against installed library when running lldb test with gcc-4.9.2
Needs ReviewPublic

Authored by chying on May 20 2015, 6:08 PM.

Details

Summary

-Read location of compiler and find library path based on that
-Set -L option to CXXFLAGS which will be used during linking and set LD_LIBRARY_PATH to shell environment

Diff Detail

Event Timeline

chying updated this revision to Diff 26199.May 20 2015, 6:08 PM
chying retitled this revision from to Link against installed library when running lldb test with gcc-4.9.2.
chying updated this object.
chying edited the test plan for this revision. (Show Details)
chying added reviewers: sivachandra, vharron.
chying added a subscriber: Unknown Object (MLST).
vharron added inline comments.May 26 2015, 3:59 PM
zorg/buildbot/builders/LLDBBuilder.py
294

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?

chying added inline comments.May 26 2015, 4:27 PM
zorg/buildbot/builders/LLDBBuilder.py
294

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?