public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: mrjre@hotmail.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/6485: compile failure
Date: Fri, 26 Apr 2002 23:16:00 -0000	[thread overview]
Message-ID: <20020427060948.24353.qmail@sources.redhat.com> (raw)


>Number:         6485
>Category:       c++
>Synopsis:       compile failure
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Apr 26 23:16:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Bonito
>Release:        gcc-3.0.4
>Organization:
>Environment:
LFS 3.3 intel 700mhz IA32 processor, 256 mb ram, 1.5 gb partition,
>Description:
kdemultimedia-3.0 with gcc-3.0.4 raised an internal compiler error:

source='playmidi.c' object='playmidi.o' libtool=no \
depfile='.deps/playmidi.Po' tmpdepfile='.deps/playmidi.TPo' \
depmode=gcc3 /bin/sh ../../admin/depcomp \
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/X11R6/include `/usr/local/kde/bin/artsc-config --cflags`  -DQT_THREAD_SUPPORT  -D_REENTRANT -DDEFAULT_PATH=\"//usr/local/kde/share/apps/kmidi/config\" -DAU_OSS  -DIA_XAW -DQT_THREAD_SUPPORT  -D_REENTRANT  -fasm -O2  -O3 -march=i686 -c `test -f playmidi.c || echo './'`playmidi.c
source='resample.c' object='resample.o' libtool=no \
depfile='.deps/resample.Po' tmpdepfile='.deps/resample.TPo' \
depmode=gcc3 /bin/sh ../../admin/depcomp \
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/X11R6/include `/usr/local/kde/bin/artsc-config --cflags`  -DQT_THREAD_SUPPORT  -D_REENTRANT -DDEFAULT_PATH=\"//usr/local/kde/share/apps/kmidi/config\" -DAU_OSS  -DIA_XAW -DQT_THREAD_SUPPORT  -D_REENTRANT  -fasm -O2  -O3 -march=i686 -c `test -f resample.c || echo './'`resample.c
resample.c: In function `pre_resample':
resample.c:1298: Internal compiler error in print_rtl_and_abort, at flow.c:6458
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[3]: *** [resample.o] Error 1
make[3]: Leaving directory `/usr/src/kde/kdemultimedia-3.0/kmidi/TIMIDITY'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/kde/kdemultimedia-3.0/kmidi'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/kde/kdemultimedia-3.0'
make: *** [all] Error 2
>How-To-Repeat:
I am not sure if it is something repeatable, I am going to try but the way I got the error was trying to compile kdemultimedia-3.0 from the sourcee .bz2 tarball that I obtained from the kde server.  unpack the directory, enter the directory, type ./configure and then make all.  I also set the flags to optimize for an i686 architecture: 

export CFLAGS="-O3 -march=i686" && CXXFLAGS=$CFLAGS
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-04-27  6:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26 23:16 mrjre [this message]
2002-06-05  8:23 lerdsuwa
2002-10-23  7:11 reichelt

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=20020427060948.24353.qmail@sources.redhat.com \
    --to=mrjre@hotmail.com \
    --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).