Might be an easy fix to have our test suite unset the "LD_LIBRARY_PATH" env var
if it is set?
> On Jan 19, 2021, at 5:38 PM, David Blaikie via lldb-dev
> wrote:
>
> Jonas helped me out here (Thanks!)
>
> Seems I was setting LD_LIBRARY_PATH for, so far as I recall, good reasons (I
> have some
Jonas helped me out here (Thanks!)
Seems I was setting LD_LIBRARY_PATH for, so far as I recall, good reasons
(I have some things installed locally in $HOME/install and I thought
somewhere in the mists of time the executables ($HOME/install/bin) didn't
naturally find some shared libraries in $HOME/
On Linux (Ubuntu) + cmake + ninja, it seems this test isn't testing the
checked-out lldb, but instead running the system (or user-dir, in my case)
installed lldb (see examples at the end of this email)
If I remove the user-dir installed lldb then the test fails differently -
complaining that it ca
