jgtong

Is there any update to this problem? I am blocked by this issue with a workload that I am trying to compile on the AMD platforms.

> I found the reason for the issue I described [here](https://github.com/intel/llvm/issues/6089#issuecomment-1120488285). The problem was that a path to `LLD` was not in `PATH` therefore the default linker was used causing...

> I added `build/bin` path to `PATH` variable and it helped. Per my understanding, `lld` command should work so that linking step can work as expected for AMD target. Interesting,...

> jfyi, I used [49f72fa](https://github.com/intel/llvm/commit/49f72fa9ee6ac500e7f8277fa5ccabff88aaff2b) @densamoilov I tried your suggestion again using the hash commit, rebuilt the llvm compiler and included the `build/bin/` and `build/install/bin` as part of my path....

@mpanoop : Here is the build log for the above command ``` clang version 15.0.0 (https://github.com/intel/llvm 6d04aa6462eb9b63ef2127cd56afdc408e3e32d4) Target: x86_64-unknown-linux-gnu Thread model: posix InstalledDir: /home/jaytong/sycl_workspace/llvm/build/bin "clang-offload-bundler" "-type=ao" "-targets=host-x86_64-unknown-linux-gnu" "-input=../libethcore/libethcore.a" "-check-section" "clang-offload-bundler"...

> @jgtong, this should be addressed with #6498, can you confirm and close as appropriate? @mdtoguchi : I can confirm that this issue has been resolved. Thank you!