public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: niallm-wan@enigma.ie To: gcc-gnats@gcc.gnu.org Subject: c++/8422: g++ 3.2 fails with internal compiler error on suse 8.1 Date: Fri, 01 Nov 2002 06:16:00 -0000 [thread overview] Message-ID: <20021101141519.916.qmail@sources.redhat.com> (raw) >Number: 8422 >Category: c++ >Synopsis: g++ 3.2 fails with internal compiler error on suse 8.1 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Nov 01 06:16:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: niallm-wan@enigma.ie >Release: gcc-3.2 >Organization: >Environment: SuSE 8.1, gcc 3.2 >Description: When compiling kismetwireless 2.6.2 (www.kismetwireless.net) on SuSE 8.1 with gcc 3.2, make prints the following sequence of errors: niallm@linux:/opt/src/kismet-2.6.2% make g++ -Ilibpcap-2002.07.02 -O2 -Wall -DVERSION_MAJOR=2 -DVERSION_MINOR=6 -DVERSION_TINY=2 -g -O2 -g -O2 -c speech.cc -o speech.o /usr/include/g++/bits/basic_string.h: In function `std::string ExpandSpeechString(std::basic_string<char, std::char_traits<char>, std::allocator<char> >, const packet_info*, int)': /usr/include/g++/bits/basic_string.h:338: Internal compiler error in expand_call, at calls.c:3049 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. make: *** [speech.o] Error 1 >How-To-Repeat: See description >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-11-01 14:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-01 6:16 niallm-wan [this message] 2002-11-01 6:45 paolo
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=20021101141519.916.qmail@sources.redhat.com \ --to=niallm-wan@enigma.ie \ --cc=gcc-gnats@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: linkBe 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).