fix: real argv[0] via SYS_GETEXECPATH - GCC driver finds its backends
The GCC driver relocates its install prefix from argv[0]. crt1 hardcoded argv[0] as "prog", so make_relative_prefix cwd-joined it and computed exec prefixes relative to the current directory (0:/users/admin/../libexec/gcc/...), and because the computed gcc_exec_prefix is non-NULL the standard /sdk prefixes were never searched. cc1plus was unreachable from anywhere except (by accident of the path arithmetic) 0:/sdk/bin. sdk-diag proved the kernel and libc layers all worked; only the driver's self-relocation was lost. New SYS_GETEXECPATH (151) returns the absolute path the process was spawned from (Process::name); crt1 uses it for argv[0] with a "prog" fallback. With a real argv[0], make_relative_prefix computes 0:/sdk/bin/../libexec/gcc/ from any cwd. Native GCC relinked against the new crt1; sdk-diag ships in the SDK as a permanent probe; the montauk.h TCC mirror gains the wrapper (checker enforced it). Co-Authored-By: Claude Fable 5 <[email protected]>
This commit is contained in:
@@ -405,6 +405,7 @@ ifneq ($(wildcard $(NATIVE_BIN)/as),)
|
||||
cp -r ../toolchain/local/x86_64-montauk/include/c++ $(BINDIR)/sdk/include/c++
|
||||
../toolchain/local/bin/x86_64-montauk-gcc -O2 ../toolchain/files/tls-test.c -o $(BINDIR)/sdk/bin/tls-test.elf
|
||||
../toolchain/local/bin/x86_64-montauk-g++ -O2 ../toolchain/files/cxx-test.cpp -o $(BINDIR)/sdk/bin/cxx-test.elf
|
||||
../toolchain/local/bin/x86_64-montauk-gcc -O2 ../toolchain/files/sdk-diag.c -o $(BINDIR)/sdk/bin/sdk-diag.elf
|
||||
ifneq ($(wildcard ../toolchain/native-gcc/sdk/bin/gcc),)
|
||||
cp ../toolchain/native-gcc/sdk/bin/gcc $(BINDIR)/sdk/bin/gcc.elf
|
||||
cp ../toolchain/native-gcc/sdk/bin/g++ $(BINDIR)/sdk/bin/g++.elf
|
||||
|
||||
Reference in New Issue
Block a user