https://github.com/dzhidzhoev updated 
https://github.com/llvm/llvm-project/pull/110837

>From a2c8b8b88fd47cbbdc32ca5f0f051391a9d77823 Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev <vdzhidzh...@accesssoftek.com>
Date: Tue, 1 Oct 2024 13:14:25 +0200
Subject: [PATCH] [lldb][test] Provide proper path to LLVM utils in API tests

In aea066849, API tests were supposed to be switched to LLVM tools
usage.
However, a path to an utility is made up incorrectly there: util name
should be prefixed with `llvm-`.

Hence it is fixed here.
---
 lldb/packages/Python/lldbsuite/test/builders/builder.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lldb/packages/Python/lldbsuite/test/builders/builder.py 
b/lldb/packages/Python/lldbsuite/test/builders/builder.py
index e3099219e437e3..f813d68e46e82a 100644
--- a/lldb/packages/Python/lldbsuite/test/builders/builder.py
+++ b/lldb/packages/Python/lldbsuite/test/builders/builder.py
@@ -176,7 +176,7 @@ def getToolchainUtil(util_name):
                 for var, name in util_names.items():
                     # Do not override explicity specified tool from the cmd 
line.
                     if not os.getenv(var):
-                        util_paths[var] = getToolchainUtil(name)
+                        util_paths[var] = getToolchainUtil("llvm-" + name)
                     else:
                         util_paths[var] = os.getenv(var)
                 utils.extend(["AR=%s" % util_paths["ARCHIVER"]])

_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

Reply via email to