While in chroot and building the final system, I noticed stage1 clang uses GCC: <d

Say, if I rename the "GCC installation" directory: <div class="snippet-clipboard-c

Renaming /llvmtools/lib/gcc and <code class="notransl

Stage1 Clang uses GCC about cmlfs HOT 3 CLOSED

dslm4515 commented on June 12, 2024

Stage1 Clang uses GCC

from cmlfs.

Comments (3)

dslm4515 commented on June 12, 2024

Looks like it might be dependent on the default linker, binutils' ld or LLVM's LLD: Why clang selects a gcc installation?

I can't remember if i saw Found candidate GCC installation posted when GCC was not installed in llvmtools.

But LLVM runtimes are used:

ld.lld: /usr/lib/Scrt1.o
ld.lld: /usr/lib/crti.o
ld.lld: /llvmtools/lib/clang/15.0.5/lib/x86_64-pc-linux-musl/clang_rt.crtbegin.o
ld.lld: /tmp/dummy-87d086.o
ld.lld: /llvmtools/lib/clang/15.0.5/lib/x86_64-pc-linux-musl/libclang_rt.builtins.a
ld.lld: /llvmtools/bin/../lib/x86_64-pc-linux-musl/libunwind.so
ld.lld: /usr/lib/libc.so
ld.lld: /llvmtools/lib/clang/15.0.5/lib/x86_64-pc-linux-musl/libclang_rt.builtins.a
ld.lld: /llvmtools/bin/../lib/x86_64-pc-linux-musl/libunwind.so
ld.lld: /llvmtools/lib/clang/15.0.5/lib/x86_64-pc-linux-musl/clang_rt.crtend.o
ld.lld: /usr/lib/crtn.o

from cmlfs.

dslm4515 commented on June 12, 2024

Say, if I rename the "GCC installation" directory:

mv -v /llvmtools/lib/gcc /llvmtools/lib/gcc-BLOCKED

Now stage1 clang doesn't use GCC!

llvmtools 3.0.0 clang version 15.0.5
Target: x86_64-pc-linux-musl
Thread model: posix
InstalledDir: /llvmtools/bin
Configuration file: /llvmtools/bin/x86_64-pc-linux-musl.cfg
"/llvmtools/bin/clang-15" -cc1 -triple x86_64-pc-linux-musl -emit-obj -mrelax-all --mrelax-relocations -disable-free -clear-ast-before-backend -disab>
clang -cc1 version 15.0.5 based upon LLVM 15.0.5 default target x86_64-pc-linux-musl

from cmlfs.

dslm4515 commented on June 12, 2024

Renaming /llvmtools/lib/gcc and /usr/lib/gcc does not affect clang but forces clang not to use GCC start files or runtime.

from cmlfs.

Recommend Projects