public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/14626] Compile fails at stage2
Date: Thu, 18 Mar 2004 09:10:00 -0000	[thread overview]
Message-ID: <20040318091013.21230.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040318013053.14626.ehicks@binarymagi.com>


------- Additional Comments From ebotcazou at gcc dot gnu dot org  2004-03-18 09:10 -------
To clarify a bit, you need a 64-bit compiler to bootstrap a 64-bit compiler. 
Either a native 64-bit compiler (sparc64-*-* or sparcv9-*-*) or a multi-arch
32-bit compiler invoked with 'gcc -m64'.

Note, however, that Ada does not appear to work for the non-default arch of a
multi-arch compiler (that is, 'gcc -m64' cannot bootstrap a 64-bit Ada compiler).


-- 


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


  parent reply	other threads:[~2004-03-18  9:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-18  1:30 [Bug bootstrap/14626] New: " ehicks at binarymagi dot com
2004-03-18  2:12 ` [Bug bootstrap/14626] " pinskia at gcc dot gnu dot org
2004-03-18  2:25 ` ehicks at binarymagi dot com
2004-03-18  2:59 ` pinskia at gcc dot gnu dot org
2004-03-18  9:10 ` ebotcazou at gcc dot gnu dot org [this message]
2004-03-18 19:17 ` [Bug ada/14626] make gnatlib_and_tools problem on cross compiler (formerly: Compile fails at stage2) ehicks at binarymagi dot com
2004-03-18 19:20 ` ehicks at binarymagi dot com
2004-03-18 19:23 ` pinskia at gcc dot gnu dot org
2004-03-19 17:51 ` ehicks at binarymagi dot com
2004-03-19 20:12 ` ehicks at binarymagi dot com
2004-03-19 21:51 ` charlet at act-europe dot fr
2004-04-27 14:04 ` pinskia 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=20040318091013.21230.qmail@sources.redhat.com \
    --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).