public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: Peter.Schoen1@epost.de, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: c++/8363: g++ 3.2 crashes with an internal compiler error when compiling STLport 4.5.3.
Date: Tue, 29 Oct 2002 15:41:00 -0000	[thread overview]
Message-ID: <20021029234137.30326.qmail@sources.redhat.com> (raw)

Synopsis: g++ 3.2 crashes with an internal compiler error when compiling STLport 4.5.3.

State-Changed-From-To: feedback->closed
State-Changed-By: bangerth
State-Changed-When: Tue Oct 29 15:41:37 2002
State-Changed-Why:
    Reporter mailed this:
    ----------------------------------------
    Hello Wolfgang,
    
    On Monday 28 October 2002 23:25, you wrote:
    > Synopsis: g++ 3.2 crashes with an internal compiler error when compiling
    > STLport 4.5.3.
    > 
    > State-Changed-From-To: open->feedback
    > State-Changed-By: bangerth
    > State-Changed-When: Mon Oct 28 14:25:34 2002
    > State-Changed-Why:
    >     I cannot reproduce your problem, although I have almost the
    >     same setup. However, I notice that you have bootstrapped
    >     your compiler in a subdirectory of the source dir. This is
    >     not the recommended way.
    
    I used the compiler provided by SuSE... After compiling gcc myself, the
    problem didn't occur anymore, now stlport compiles without a problem. Guess I
    should switch to Gentoo ;-)
    
    Very best wishes
    
    -Peter Schoen

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8363


             reply	other threads:[~2002-10-29 23:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-29 15:41 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-28 14:25 bangerth

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=20021029234137.30326.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=Peter.Schoen1@epost.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --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).