http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59321
Bug ID: 59321 Summary: -fuse-ld does not have effect on -print-prog-name Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: driver Assignee: unassigned at gcc dot gnu.org Reporter: maemarcus at gmail dot com Many configure scripts e.g. GLIBC use -print-prog-name to check the binary utils used by GCC. Distros may face need to switch linker between bfd and gold, which is now possible thanks to -fuse-ld flag. However, -print-prog-name is not affected by -fuse-ld, and thus may lead to configure checks and actual build being performed using different linkers. $ kernelgen-gcc -fuse-ld=gold -print-prog-name=ld /home/marcusmae/rpmbuild/kernelgen/head_llvm192445_i686-linux-gnu_x86_64-linux-gnu_debug/INSTALL/bin/kernelgen-ld $ kernelgen-gcc -fuse-ld=bfd -print-prog-name=ld /home/marcusmae/rpmbuild/kernelgen/head_llvm192445_i686-linux-gnu_x86_64-linux-gnu_debug/INSTALL/bin/kernelgen-ld I think -fuse-ld should play together with -print-prog-name. In the example above with default gold, second command should point to kernelgen-ld.bfd