Ah, yes, it does. It looks like it does contain /usr/bin.
Script Arguments:
Arch: 64
Compiler: any
Outdir:
/vstsdrive/_work/42/b/LLVMBuild/tools/lldb/lit/tools/lldb-mi/exec/Output
Output:
/vstsdrive/_work/42/b/LLVMBuild/tools/lldb/lit/tools/lldb-mi/exec/Output/exec-next-instruction.test.
Don't we print the environment in verbose mode? Can we see that output as
well?
On Fri, Dec 14, 2018 at 11:53 AM Stella Stamenova
wrote:
> The verbose output is below. If I run the two commands on the command
> line, they both succeed, but when I run them through build.py, the link
> command is
The verbose output is below. If I run the two commands on the command line,
they both succeed, but when I run them through build.py, the link command is
failing. I suspect that the process that gets created through python doesn't
inherit the environment with the PATH set, so it can't find the li
On 14/12/2018 20:32, Stella Stamenova via Phabricator wrote:
stella.stamenova added a comment.
I am trying to use the new builder to build the lldb-mi tests, so that they can
start consistently passing on Windows, so they're now using the gcc builder on
Linux and failing:
Interesting. Can yo
It's fine, I was mostly just curious.
On Wed, Dec 12, 2018 at 8:52 AM Pavel Labath via Phabricator <
revi...@reviews.llvm.org> wrote:
> labath marked an inline comment as done.
> labath added inline comments.
>
>
>
> Comment at: lldb/trunk/lit/helper/build.py:630
> +a
