https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42679
maemarcus at gmail dot com changed:
What|Removed |Added
CC||maemarcus at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59321
--- Comment #17 from maemarcus at gmail dot com ---
Works as a charm! Many thanks!
$ manual-gcc -print-prog-name=ld
/media/scratch/manual/binutils-2.24.51/build32_glibc/install/bin/manual-ld
$ manual-gcc -fuse-ld=bfd -print-prog-name=ld
/media
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59321
--- Comment #10 from maemarcus at gmail dot com ---
Right, I guess the reason of the difference is I'm configured with
--program-prefix=kernelgen-
--with-ld=$RPM_INSTALL_PREFIX/%{prefix}bin/kernelgen-ld
--with-as=$RPM_INSTALL_PREFIX/%{prefi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59321
--- Comment #8 from maemarcus at gmail dot com ---
Dear H.J. Lu,
You patch works for me, thanks a lot! I noticed however, that with -fuse-ld ld
from the different location is used for me:
$ kernelgen-gcc -print-prog-name=ld
.../INSTALL/bin
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59321
--- Comment #3 from maemarcus at gmail dot com ---
I'm only saying configure scripts use -print-prog-name to determine the linker,
and with introduction of -fuse-ld what's returned there could be inconsistent
with what linker is actu
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
