fix: /cgnutools/include/$TARGET_TUPLE/c++/v1 for __config_site at LLV…

[takusuman]

…M 1st stage

Discovered this while building Copacabana's toolchain. Fixes #72.

[dslm4515]

For the 2nd line edit, I think you forgot to use $TARGET_TUPLE instead of a architecture-specific one

[takusuman]

For the 2nd line edit, I think you forgot to use $TARGET_TUPLE instead of a architecture-specific one

Sure, just one minute.

[takusuman]

Well, I think this also happens in other parts of the file, take a look:

CMLFS/1-Stage0/7-LLVM.stage0

Lines 162 to 174 in 4de6732

	# Should output:
	# ld.lld: /llvmtools/lib/Scrt1.o
	# ld.lld: /llvmtools/lib/crti.o
	# ld.lld: /mnt/cmlfs/cgnutools/lib/clang/17/lib/x86_64-pc-linux-musl/clang_rt.crtbegin.o
	# ld.lld: /tmp/dummy-ffb57c.o
	# ld.lld: /mnt/cmlfs/cgnutools/lib/clang/17/lib/x86_64-pc-linux-musl/libclang_rt.builtins.a
	# ld.lld: /llvmtools/lib/libunwind.so
	# ld.lld: /llvmtools/lib/libatomic.so
	# ld.lld: /llvmtools/lib/libc.so
	# ld.lld: /mnt/cmlfs/cgnutools/lib/clang/17/lib/x86_64-pc-linux-musl/libclang_rt.builtins.a
	# ld.lld: /llvmtools/lib/libunwind.so
	# ld.lld: /mnt/cmlfs/cgnutools/lib/clang/17/lib/x86_64-pc-linux-musl/clang_rt.crtend.o
	# ld.lld: /llvmtools/lib/crtn.o

That's why I used an architecture-specific example, and I think we could also assume that someone who's reading CMLFS knows that there are parts of the expected lld --- or pretty much any other verification --- output that will be architecture specific.