public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ljrittle@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
troger@acxiom.com
Subject: Re: bootstrap/3484: Dies during build
Date: Fri, 24 Aug 2001 14:26:00 -0000 [thread overview]
Message-ID: <20010824212653.12528.qmail@sourceware.cygnus.com> (raw)
Synopsis: Dies during build
State-Changed-From-To: open->closed
State-Changed-By: ljrittle
State-Changed-When: Fri Aug 24 14:26:53 2001
State-Changed-Why:
Fixed on mainline and 3.0.1. (to avoid your next
problem:) If you don't already, please configure gcc to
build outside the source tree.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3484&database=gcc
next reply other threads:[~2001-08-24 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-24 14:26 ljrittle [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-29 12:06 troger
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=20010824212653.12528.qmail@sourceware.cygnus.com \
--to=ljrittle@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
--cc=troger@acxiom.com \
/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).