public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "krejzi at email dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/53662] Cannot build static gcc on i686 linux gnu with -m64 support.
Date: Wed, 13 Jun 2012 21:17:00 -0000	[thread overview]
Message-ID: <bug-53662-4-XATi0qm1P1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53662-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Armin K. <krejzi at email dot com> 2012-06-13 21:17:35 UTC ---
(In reply to comment #1)
> 
> That means you need a 64-bit capable binutils.
> 
> Just a guess, but you might need to use --target=x86_64-unknown-linux-gnu to
> make a cross compiler for x86_64, which will be multilib-capable by default. 
> To do that you'll need a 64-bit binutils and 64-bit glibc.
> 
> This should really be dealt with on the gcc-help mailing list, I don't think
> it's a bug.

Sorry, I meant that this might be bug in gcc bootstrap stage. As I said, I have
compiled binutils with --enable-multilib ... I could try --enable-64-bit-bfd
tough. Also, what is gcc-help mailing list address?


  parent reply	other threads:[~2012-06-13 21:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13 20:56 [Bug c/53662] New: " krejzi at email dot com
2012-06-13 21:13 ` [Bug c/53662] " redi at gcc dot gnu.org
2012-06-13 21:17 ` krejzi at email dot com [this message]
2012-06-13 23:12 ` redi at gcc dot gnu.org
2012-11-26  4:01 ` bugfeed at online dot de
2014-06-30 19:33 ` mpolacek at gcc dot gnu.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=bug-53662-4-XATi0qm1P1@http.gcc.gnu.org/bugzilla/ \
    --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).