public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fw at deneb dot enyo dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/12614] [3.3 regression] Can't bootstrap without gnatmake
Date: Tue, 14 Oct 2003 15:11:00 -0000	[thread overview]
Message-ID: <20031014151119.8173.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031014131549.12614.schwab@suse.de>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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


fw at deneb dot enyo dot de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  BugsThisDependsOn|                            |5911
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1


------- Additional Comments From fw at deneb dot enyo dot de  2003-10-14 15:11 -------
Documenting the dependency on the build system overhaul.


  parent reply	other threads:[~2003-10-14 15:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-14 13:15 [Bug bootstrap/12614] New: " schwab at suse dot de
2003-10-14 13:43 ` [Bug bootstrap/12614] " ro at techfak dot uni-bielefeld dot de
2003-10-14 14:51 ` schwab at suse dot de
2003-10-14 14:57 ` fw at deneb dot enyo dot de
2003-10-14 15:07 ` schwab at suse dot de
2003-10-14 15:11 ` fw at deneb dot enyo dot de [this message]
2003-10-14 20:10 ` jsm at polyomino dot org dot uk
2003-10-21 17:05 ` charlet at gcc dot gnu dot org
2003-11-08 21:05 ` dhazeghi at yahoo dot com
2003-11-12 22:00 ` ro at techfak dot uni-bielefeld dot de
2003-12-08 10:07 ` cvs-commit at gcc dot gnu dot org
2003-12-08 10:08 ` charlet 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=20031014151119.8173.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).