From 5ef37602345771f2fa1702ee878d9e27b4d54c40 Mon Sep 17 00:00:00 2001 From: Deven Desai Date: Mon, 7 Dec 2020 15:07:03 +0000 Subject: [PATCH] Removing --action_env=ROCM_ROOT... when building with --config=rocm When we switched to ROCm 3.3 (first ROCm release with "relocatable ROCm install" support), some parts of the ROCm toolchain relied upon the value of env var ROCM_ROOT to determine the location of the ROCm install dir. This has been fixed, and all of the ROCM toolchain now only uses the ROCM_PATH value. This commit updates `configure.py` to no longer set ROCM_ROOT, when building with --config=rocm Related JIRA ticket - http://ontrack-internal.amd.com/browse/SWDEV-226744 --- configure.py | 1 - 1 file changed, 1 deletion(-) diff --git a/configure.py b/configure.py index 521f5d9cb98..1207986739e 100644 --- a/configure.py +++ b/configure.py @@ -1333,7 +1333,6 @@ def main(): if (environ_cp.get('TF_NEED_ROCM') == '1' and environ_cp.get('ROCM_PATH')): write_action_env_to_bazelrc('ROCM_PATH', environ_cp.get('ROCM_PATH')) - write_action_env_to_bazelrc('ROCM_ROOT', environ_cp.get('ROCM_PATH')) if ((environ_cp.get('TF_NEED_ROCM') == '1') and (environ_cp.get('TF_ENABLE_MLIR_GENERATED_GPU_KERNELS') == '1')):