Your message dated Mon, 04 Jul 2005 11:30:33 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#316323: FTBFS: internal errors: lower_stmt error and
segmentation fault
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 30 Jun 2005 05:45:33 +0000
>From [EMAIL PROTECTED] Wed Jun 29 22:45:33 2005
Return-path: <[EMAIL PROTECTED]>
Received: from snoopy.microcomaustralia.com.au [202.173.153.89]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Dnrrh-0001oG-00; Wed, 29 Jun 2005 22:45:33 -0700
Received: from localhost (localhost [127.0.0.1])
by snoopy.microcomaustralia.com.au (Postfix) with ESMTP id 0BEF4D8BDA
for <[EMAIL PROTECTED]>; Thu, 30 Jun 2005 15:45:30 +1000 (EST)
Received: from snoopy.microcomaustralia.com.au ([127.0.0.1])
by localhost (snoopy [127.0.0.1]) (amavisd-new, port 10024) with LMTP
id 09985-08-2 for <[EMAIL PROTECTED]>;
Thu, 30 Jun 2005 15:45:22 +1000 (EST)
Received: by snoopy.microcomaustralia.com.au (Postfix, from userid 10003)
id 6D5E3D8760; Thu, 30 Jun 2005 15:45:22 +1000 (EST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Brian May <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: FTBFS: internal errors: lower_stmt error and segmentation fault
X-Mailer: reportbug 3.8
Date: Thu, 30 Jun 2005 15:45:22 +1000
Message-Id: <[EMAIL PROTECTED]>
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at snoopy.apana.org.au
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: gcc-4.0
Severity: serious
Justification: no longer builds from source
Hello,
I am trying to compile gcc-4.0 on Ubuntu, so I can recompile the
latest openoffice.org2 package.
However, I get different errors each time. I don't think these are ubuntu
specific. If you consider this the wrong forum for such bug reports, please let
me know.
Rather then not include enough details, I will give everything I still have
just in case it helps.
The 1st compile attempt I got the following error:
--- cut ---
stage2/xgcc -Bstage2/ -B/usr/i486-linux-gnu/bin/ -c -O2 -DIN_GCC -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic
-Wno-long-long -Wno-variadic-macros -Wold-style-definition -DHAVE_CONFIG_H
-I. -I. -I../../src/gcc -I../../src/gcc/. -I../../src/gcc/../include
-I../../src/gcc/../libcpp/include ../../src/gcc/predict.c -o predict.o
../../src/gcc/predict.c: In function 'estimate_loops_at_level':
../../src/gcc/predict.c:1705: internal compiler error: in lower_stmt, at
gimple-low.c:206
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:///usr/share/doc/gcc-4.0/README.Bugs>.
make[4]: *** [predict.o] Error 1
make[4]: Leaving directory `/tmp/buildd/gcc-4.0-4.0.0ds1/build/gcc'
make[3]: *** [stage3_build] Error 2
make[3]: Leaving directory `/tmp/buildd/gcc-4.0-4.0.0ds1/build/gcc'
make[2]: *** [bootstrap] Error 2
make[2]: Leaving directory `/tmp/buildd/gcc-4.0-4.0.0ds1/build'
s=`cat status`; rm -f status; test $s -eq 0
make[1]: *** [stamps/05-build-stamp] Error 1
make[1]: Leaving directory `/tmp/buildd/gcc-4.0-4.0.0ds1'
make: *** [stamps/05-build-stamp] Error 2
pbuilder: Failed autobuilding of package
-> Aborting with an error
-> unmounting dev/pts filesystem
-> unmounting proc filesystem
-> cleaning the build env
-> removing directory /var/cache/pbuilder/build//27869 and its
subdirectories
--- cut ---
At first, this looked like the bug reported at
<URL:http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16254>, however, this bug is
meant to have been fixed already.
Using a new clean pbuilder ubuntu hoary chroot, I attempted the same operation
again, and got a different error. This leaves me very puzzled if it is the same
bug or a new bug (I apologise if you think I should have opened two bug
reports). This time I got the following output:
--- cut ---
stage2/xgcc -Bstage2/ -B/usr/i486-linux-gnu/bin/ -c -O2 -DIN_GCC -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic
-Wno-long-long -Wno-variadic-macros -Wold-style-definition -DHAVE_CONFIG_H
-I. -Icp -I../../src/gcc -I../../src/gcc/cp -I../../src/gcc/../include
-I../../src/gcc/../libcpp/include ../../src/gcc/cp/pt.c -o cp/pt.o
../../src/gcc/cp/pt.c: In function 'tsubst':
../../src/gcc/cp/pt.c:6901: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:///usr/share/doc/gcc-4.0/README.Bugs>.
make[4]: *** [cp/pt.o] Error 1
make[4]: Leaving directory `/tmp/buildd/gcc-4.0-4.0.0ds1/build/gcc'
make[3]: *** [stage3_build] Error 2
make[3]: Leaving directory `/tmp/buildd/gcc-4.0-4.0.0ds1/build/gcc'
make[2]: *** [bootstrap] Error 2
make[2]: Leaving directory `/tmp/buildd/gcc-4.0-4.0.0ds1/build'
s=`cat status`; rm -f status; test $s -eq 0
make[1]: *** [stamps/05-build-stamp] Error 1
make[1]: Leaving directory `/tmp/buildd/gcc-4.0-4.0.0ds1'
make: *** [stamps/05-build-stamp] Error 2
pbuilder: Failed autobuilding of package
-> Aborting with an error
-> unmounting dev/pts filesystem
-> unmounting proc filesystem
-> cleaning the build env
-> removing directory /var/cache/pbuilder/build//13539 and its
subdirectories
--- cut ---
Any work arounds appreciated.
Thanks
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-k7
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
---------------------------------------
Received: (at 316323-done) by bugs.debian.org; 4 Jul 2005 09:31:06 +0000
>From [EMAIL PROTECTED] Mon Jul 04 02:31:06 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp07.web.de [217.72.192.225]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DpNI9-0003hy-00; Mon, 04 Jul 2005 02:31:06 -0700
Received: from [82.82.254.140] (helo=juist)
by smtp07.web.de with asmtp (TLSv1:DES-CBC3-SHA:168)
(WEB.DE 4.105 #297)
id 1DpNHe-0006c2-00
for [EMAIL PROTECTED]; Mon, 04 Jul 2005 11:30:35 +0200
Received: from falk by juist with local (Exim 4.51)
id 1DpNHd-0000JF-DU
for [EMAIL PROTECTED]; Mon, 04 Jul 2005 11:30:33 +0200
To: [EMAIL PROTECTED]
Subject: Re: Bug#316323: FTBFS: internal errors: lower_stmt error and
segmentation fault
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
From: Falk Hueffner <[EMAIL PROTECTED]>
X-Face: "iUeUu$b*W_"w?tV83Y3*r:`rh&dRv}$YnZ3,LVeCZSYVuf[Gpo*5%_=/\_!gc_,SS}[~xZ
wY77I-M)xHIx:2f56g%/`SOw"Dx%4Xq0&f\Tj~>|QR|vGlU}TBYhiG(K:2<T^
Date: Mon, 04 Jul 2005 11:30:33 +0200
In-Reply-To: <[EMAIL PROTECTED]> (Brian May's
message of "Mon, 04 Jul 2005 19:17:35 +1000")
Message-ID: <[EMAIL PROTECTED]>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.5 (cilantro, linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: [EMAIL PROTECTED]
X-Sender: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Brian May <[EMAIL PROTECTED]> writes:
> Please close this bug report.
OK.
--
Falk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
