Sergei Trofimovich 649ebfbed6 cc-wrapper: change cflags order from cc/crt1/libc to crt1/libc/cc ... In https://github.com/NixOS/nixpkgs/issues/158042 I noticed order mismatch as a bootstrap build failure when building x86_64-linux against glibc-2.35 in nixpkgs (bootstrap libs has glibc-2.27): expand-response-params> ld: /nix/store/p4s4jf7aq6v6z9iazll1aiqwb34aqxq9-bootstrap-tools/lib/crt1.o: in function `_start': expand-response-params> /build/glibc-2.27/csu/../sysdeps/x86_64/start.S:101: undefined reference to `__libc_csu_fini' expand-response-params> ld: /build/glibc-2.27/csu/../sysdeps/x86_64/start.S:102: undefined reference to `__libc_csu_init' expand-response-params> collect2: error: ld returned 1 exit status Here crt1.o from glibc-2.27 links against libc.so.6 from glibc-2.35. This happens because ordering of `-L` (influences `libc.so` lookup) and `-B` (influences `crt1.o` lookup) flags differs: expand-response-params> -B/...-bootstrap-tools/lib expand-response-params> -B/...-glibc-2.35/lib/ ... expand-response-params> -L/...-glibc-2.35/lib expand-response-params> -L/...-bootstrap-tools/lib The change makes consistent ordering of `-L`/`-B` and allows getting to stage4 for `glibc-2.35` target.		2022-02-20 10:45:45 +00:00
..
add-flags.sh	cc-wrapper: change cflags order from cc/crt1/libc to crt1/libc/cc	2022-02-20 10:45:45 +00:00
add-hardening.sh	{cc,binutils}-wrapper: match leading/trailing arguments	2021-09-20 17:24:04 -07:00
cc-wrapper.sh	Check link type based on expanded parameters	2022-01-01 20:30:56 +08:00
default.nix
fortran-hook.sh
gnat-wrapper.sh
setup-hook.sh