public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/39317] [lto] - cannot compute suffix of object files - cannot represent relocation type BFD_RELOC_64
Date: Sat, 28 Feb 2009 03:53:00 -0000	[thread overview]
Message-ID: <20090228035333.26921.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39317-13830@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from rob1weld at aol dot com  2009-02-28 03:53 -------
(In reply to comment #4)
> In addition to the lack of "-L..." this is also a 'spec' issue :
> ...

The issue with the spec file is caused by this in the Makefile.in:

# Dump a specs file to make -B./ read these specs over installed ones.
$(SPECS): xgcc$(exeext)
        $(GCC_FOR_TARGET) -dumpspecs > tmp-specs
        mv tmp-specs $(SPECS)



Debian's supplied gcc 4.3 is built androgynous:

# gcc -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.2-1.1'
--with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3
--program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug
--enable-objc-gc --enable-mpfr --enable-targets=all --enable-cld
--enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu
--target=i486-linux-gnu
Thread model: posix
gcc version 4.3.2 (Debian 4.3.2-1.1) 


# gcc -dumpspecs | head -2
*asm:
%{v:-V} %{Qy:} %{!Qn:-Qy} %{n} %{T} %{Ym,*} %{Yd,*}  %{Wa,*:%*} %{m32:--32}
%{m64:--64}



We need to check that the host-compiler's "spec" is correct and fix it.


Here is some pseudo-code:

if ' gcc -dumpspecs | grep \{m32:--32 | grep \{m64:--64 ' then # not correct
  if test x`(hostname || uname -n) 2>/dev/null | sed 1q` == "xopensolaris" ;
then
    if 'isainfo -k' = 'i386' then 
      gcc -dumpspecs | sed 2s/m32:--32/!m32:--32/1p
    fi
    if 'isainfo -k' = 'amd_64' | 'x86_64' then 
      gcc -dumpspecs | sed 2s/m64:--64/!m64:--64/1p
    fi
  else # Not OpenSolaris' uname
    if 'uname -m' = 'i386' then 
      gcc -dumpspecs | sed 2s/m32:--32/!m32:--32/1p
    fi
    if 'uname -m' = 'amd_64' | 'x86_64' then 
      gcc -dumpspecs | sed 2s/m64:--64/!m64:--64/1p
    fi
  fi
fi


Rob



-- 


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


  parent reply	other threads:[~2009-02-28  3:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27  0:30 [Bug lto/39317] New: " rob1weld at aol dot com
2009-02-27  0:33 ` [Bug lto/39317] " pinskia at gcc dot gnu dot org
2009-02-27  0:34 ` pinskia at gcc dot gnu dot org
2009-02-27  1:30 ` rob1weld at aol dot com
2009-02-27  6:09 ` rob1weld at aol dot com
2009-02-28  3:53 ` rob1weld at aol dot com [this message]
2009-02-28 17:34 ` rob1weld at aol dot com
2009-03-02  3:19 ` rob1weld at aol dot com
2009-03-05 22:59 ` rob1weld at aol dot com
2009-03-06 11:08 ` rob1weld at aol dot com
2009-07-09  5:52 ` bje at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090228035333.26921.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).