http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59321
H.J. Lu changed:
What|Removed |Added
Attachment #31335|0 |1
is obsolete|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59321
H.J. Lu changed:
What|Removed |Added
Attachment #31333|0 |1
is obsolete|
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/%{prefix}bin/ke
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59321
--- Comment #9 from H.J. Lu ---
This is not what I see with GCC 4.9.0:
[hjl@gnu-tools-1 tools-4.9]$ ls release/usr/gcc-4.9.0/bin/
x86_64-linux-addr2line x86_64-linux-gcc x86_64-linux-ld.gold
x86_64-linux-ar x86_64-linux-gcc-4.9.0
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/kernel
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59321
H.J. Lu changed:
What|Removed |Added
Status|REOPENED|NEW
--- Comment #7 from H.J. Lu ---
I got
[hj
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59321
H.J. Lu changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59321
--- Comment #5 from H.J. Lu ---
Created attachment 31333
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31333&action=edit
A patch
This patch teaches gcc.c to append .bfd/.gold to ld if
-fuse-ld=XXX is used for --print-prog-name=ld.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59321
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
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 actually being used
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59321
--- Comment #2 from Andreas Schwab ---
The driver doesn't actually call ld, but collect2, and passes -fuse-ld down to
it.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59321
--- Comment #1 from H.J. Lu ---
-print-prog-name=foobar gives the path name of program, foobar.
which isn't necessarily used by the GCC driver:
[hjl@gnu-6 gcc-4.6.3-x32]$ ./bin/gcc -print-prog-name=as
as
[hjl@gnu-6 gcc-4.6.3-x32]$ ./bin/gcc -pr
12 matches
Mail list logo
