public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Daniel Rohe <rohe@physik.RWTH-Aachen.DE>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/3542: building gcc-3.0 fails on SuSE-7.1
Date: Sun, 11 Nov 2001 13:46:00 -0000 [thread overview]
Message-ID: <20011118202601.2541.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR bootstrap/3542; it has been noted by GNATS.
From: Daniel Rohe <rohe@physik.RWTH-Aachen.DE>
To: rodrigc@gcc.gnu.org
Cc: daniel.rohe@post.rwth-aachen.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
nobody@gcc.gnu.org
Subject: Re: bootstrap/3542: building gcc-3.0 fails on SuSE-7.1
Date: Tue, 30 Oct 2001 09:09:35 +0100
rodrigc@gcc.gnu.org wrote:
> Synopsis: building gcc-3.0 fails on SuSE-7.1
>
> State-Changed-From-To: open->feedback
> State-Changed-By: rodrigc
> State-Changed-When: Sun Oct 28 19:15:25 2001
> State-Changed-Why:
> Can you tell us if this still occur with gcc 3.0.2?
> We've had successful reports of gcc 3.0.x building
> on Suse Linux.
no problem, the history behind this 'bug' was rather simple
and was in the end not related to the gcc source code. I thought
this was documented in the mailing-list, but apparently I didn't
update this subject - sorry.
daniel
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=3542&database=gcc
>
>
--
Daniel Rohe
Institut fuer Theoretische Physik
Lehrstuhl C
RWTH Aachen
52056 Aachen
Tel.: 0241 8028392
next reply other threads:[~2001-11-18 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-11 13:46 Daniel Rohe [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-12 0:09 rodrigc
2001-11-11 16:36 rodrigc
2001-11-11 16:06 Craig Rodrigues
2001-10-28 19:15 rodrigc
2001-07-03 6:56 daniel.rohe
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=20011118202601.2541.qmail@sourceware.cygnus.com \
--to=rohe@physik.rwth-aachen.de \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).