On Wed, 29 May 2024 15:10:58 GMT, Jiangli Zhou wrote:
>> When compiling with clang on linux, clang can decide to pick up the bfd
>> linker instead of lld, the LLVM linker. This will invalidate assumptions
>> about command lines that are passed on to the linker. We should use
>> -fuse-ld=lld to
On Wed, 29 May 2024 15:01:27 GMT, Magnus Ihse Bursie wrote:
> When compiling with clang on linux, clang can decide to pick up the bfd
> linker instead of lld, the LLVM linker. This will invalidate assumptions
> about command lines that are passed on to the linker. We should use
> -fuse-ld=lld
On Wed, 29 May 2024 15:10:58 GMT, Jiangli Zhou wrote:
>> When compiling with clang on linux, clang can decide to pick up the bfd
>> linker instead of lld, the LLVM linker. This will invalidate assumptions
>> about command lines that are passed on to the linker. We should use
>> -fuse-ld=lld to
On Wed, 29 May 2024 15:01:27 GMT, Magnus Ihse Bursie wrote:
> When compiling with clang on linux, clang can decide to pick up the bfd
> linker instead of lld, the LLVM linker. This will invalidate assumptions
> about command lines that are passed on to the linker. We should use
> -fuse-ld=lld
When compiling with clang on linux, clang can decide to pick up the bfd linker
instead of lld, the LLVM linker. This will invalidate assumptions about command
lines that are passed on to the linker. We should use -fuse-ld=lld to force
clang to always pick lld as the linker, so we can be sure tha
