Instead of just printing the path for ld, we compile a small test program with the CFLAGS and LDFLAGS from configure and increased verbosity, and grep the linker output.
Configure script was rebuild using autoreconf -vi.
[...]
checking for runtime ABI... gnustep-2.0
checking which linker is being used... lld
checking whether the compiler supports native ObjC exceptions... yes
[...]
[...]
checking whether runtime library supports the gnustep-2.0 ABI... yes
checking for runtime ABI... gnustep-2.0
checking which linker is being used... GNU gold
checking whether the compiler supports native ObjC exceptions... yes
[...]
Otherwise
[...]
checking for runtime ABI... gnustep-2.0
checking which linker is being used... GNU ld
configure: WARNING: The detected linker (GNU ld) might not produce working Objective-C binaries using the gnustep-2.0 ABI. Consider using GNU gold or LLD.
checking whether the compiler supports native ObjC exceptions... yes
[...]
See: #36
Instead of just printing the path for ld, we compile a small test program with the CFLAGS and LDFLAGS from configure and increased verbosity, and grep the linker output.
Configure script was rebuild using
autoreconf -vi
.Demonstration:
LLD
GNU Gold
Otherwise