[Bug lto/39317] [lto] - cannot compute suffix of object files - cannot represent relocation type BFD_RELOC_64

[rob1weld at aol dot com]

------- Comment #4 from rob1weld at aol dot com  2009-02-27 06:08 -------
# uname -m
x86_64


In addition to the lack of "-L..." this is also a 'spec' issue :

Original (head -2 ../lto_build/prev-gcc/specs) :
*asm:
%{v:-V} %{Qy:} %{!Qn:-Qy} %{n} %{T} %{Ym,*} %{Yd,*}  %{Wa,*:%*} %{m32:--32}
%{m64:--64}  %{!mno-sse2avx:%{mavx:-msse2avx}} %{msse2avx:%{!mavx:-msse2avx}}

Fixed:
*asm:
%{v:-V} %{Qy:} %{!Qn:-Qy} %{n} %{T} %{Ym,*} %{Yd,*}  %{Wa,*:%*} %{m32:--32}
%{!m64:--64}  %{!mno-sse2avx:%{mavx:-msse2avx}} %{msse2avx:%{!mavx:-msse2avx}}


If I am:

# uname -m
x86_64

I need the "!" before the "m64".


If I am:

# uname -m
i386

I need the "!" before the "m32".


That defaults the compiler to build executables that match the
Boot-mode (32 or 64 bit). To build in the mode _not_ booted into
should require the appropriate "-m64" _OR_ "-m32". We should not
be required to _always_ specify either "-m64" _OR_ "-m32", there
must be a default.


Rob


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39317