public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aaronavay62 at aaronwl dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/18107] New: [4.0 Regression]  Bootstrap fails on i686-pc-mingw32
Date: Fri, 22 Oct 2004 05:18:00 -0000	[thread overview]
Message-ID: <20041022051829.18107.aaronavay62@aaronwl.com> (raw)

This is a meta-bug for all of the things causing a Windows bootstrap to fail. 
This should be closed when i686-pc-mingw32 successfully completes a full bootstrap.

-- 
           Summary: [4.0 Regression]  Bootstrap fails on i686-pc-mingw32
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Keywords: meta-bug
          Severity: critical
          Priority: P2
         Component: bootstrap
        AssignedTo: aaronavay62 at aaronwl dot com
        ReportedBy: aaronavay62 at aaronwl dot com
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-mingw32
  GCC host triplet: i686-pc-mingw32
GCC target triplet: i686-pc-mingw32
 BugsThisDependsOn: 17406,17832,18103,18104,18105


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


             reply	other threads:[~2004-10-22  5:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22  5:18 aaronavay62 at aaronwl dot com [this message]
2004-10-22  5:29 ` [Bug bootstrap/18107] " aaronavay62 at aaronwl dot com
2004-10-22 11:44 ` pinskia at gcc dot gnu dot org
2004-10-25  6:19 ` aaronavay62 at aaronwl dot com
2004-10-25 11:41 ` pinskia at gcc dot gnu dot org
2004-10-27  2:46 ` pinskia at gcc dot gnu dot org
2004-10-27 20:18 ` aaronavay62 at aaronwl dot com
2004-10-29 19:17 ` aaronavay62 at aaronwl dot com
2004-10-29 19:26 ` pinskia at gcc dot gnu dot org
2004-10-31 15:10 ` pinskia at gcc dot gnu dot org
2004-11-06  4:34 ` aaronavay62 at aaronwl dot com
2004-11-22 13:51 ` pinskia at gcc dot gnu dot org
2004-11-27  1:05 ` [Bug bootstrap/18107] [4.0 Regression] [meta-bug] " pinskia at gcc dot gnu dot org
2004-12-02  0:43 ` pbrook at gcc dot gnu dot org
2004-12-04 14:41 ` pinskia at gcc dot gnu dot org
2004-12-04 15:38 ` giovannibajo at libero dot it
2004-12-05  4:36 ` pinskia at gcc dot gnu dot org
2004-12-13 15:23 ` pinskia at gcc dot gnu dot org
2004-12-13 15:25 ` pinskia at gcc dot gnu dot org
2004-12-13 15:42 ` pinskia at gcc dot gnu dot org
2004-12-19  1:56 ` aaronavay62 at aaronwl dot com
2004-12-19 18:59 ` aaronavay62 at aaronwl dot com
2004-12-28  5:27 ` rth at gcc dot gnu dot org
2004-12-28  5:29 ` 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=20041022051829.18107.aaronavay62@aaronwl.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).