public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: d.meisen@batacs.de
To: gcc-gnats@gcc.gnu.org
Subject: other/8388: GCC- internal compiler error
Date: Mon, 28 Oct 2002 16:26:00 -0000	[thread overview]
Message-ID: <20021029002025.28233.qmail@sources.redhat.com> (raw)


>Number:         8388
>Category:       other
>Synopsis:       GCC- internal compiler error
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Oct 28 16:26:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     d.meisen@batacs.de
>Release:        gcc-3.2
>Organization:
>Environment:
Suse Linux 8.1 default Installtion
>Description:
when I try to "make" or "make all" the sources of Kismet (www.kismetwireless.net) newer and older versions I get an "internal compiler error" :

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:
configure the sources under suse 8.1, then type make
>Fix:
i dont know =)
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-10-29  0:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-28 16:26 d.meisen [this message]
2002-11-08 13:44 reichelt
2003-02-23 21:13 neroden

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=20021029002025.28233.qmail@sources.redhat.com \
    --to=d.meisen@batacs.de \
    --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: 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).