Your message dated Sat, 11 Jan 2003 12:30:57 +0100
with message-id <[EMAIL PROTECTED]>
and subject line closing FTBFS reports for gcc-3.0
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; 13 Dec 2002 06:20:33 +0000
>From [EMAIL PROTECTED] Fri Dec 13 00:20:33 2002
Return-path: <[EMAIL PROTECTED]>
Received: from mikilab.doshisha.ac.jp [202.23.156.50]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18MjBY-0008NL-00; Fri, 13 Dec 2002 00:20:32 -0600
Received: from atoron.work.isl.doshisha.ac.jp.doshisha.ac.jp (localhost
[127.0.0.1])
by mikilab.doshisha.ac.jp (8.12.3/3.7W) with ESMTP id gBD6K1QU008124
for <[EMAIL PROTECTED]>; Fri, 13 Dec 2002 15:20:01 +0900
Date: Fri, 13 Dec 2002 15:20:29 +0900
Message-ID: <[EMAIL PROTECTED]>
From: Junichi Uekawa <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: FTBFS: Build failure of gcc-3.0 on i386
User-Agent: Wanderlust/2.8.1 (Something) SEMI/1.14.4 (Hosorogi) FLIM/1.14.4
(=?ISO-8859-4?Q?Kashiharajing=FE-mae?=) APEL/10.4 Emacs/21.2
(i386-pc-linux-gnu) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi")
Content-Type: text/plain; charset=US-ASCII
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-0.5 required=5.0
tests=SPAM_PHRASE_00_01,USER_AGENT
version=2.41
X-Spam-Level:
Package: gcc-3.0
Version: 3.0.4ds3-13
Severity: serious
gcc-3.0 fails to build from source on i386, when doing a rebuild inside chroot.
I am filing this bug to notify you that I failed to build your
package from source in the current sid distribution.
It is a serious problem that your source does not
build from source using the information provided in your control files,
and such a package should not be distributed in a stable Debian distribution.
This build was done using pbuilder package.
I think is it choking on new bison.
Build log follows:
===========================================
echo timestamp > ../../src/gcc/cstamp-h.in
bison -t --name-prefix=java_ \
-o p$$.c ../../src/gcc/java/parse.y && \
mv -f p$$.c ../../src/gcc/java/parse.c
../../src/gcc/java/parse.y:513.8-13: type redeclaration for interface_type_list
../../src/gcc/java/parse.y:522.8-13: type redeclaration for
class_member_declaration
../../src/gcc/java/parse.y:535.8-13: type redeclaration for
unary_expression_not_plus_minus
../../src/gcc/java/parse.y:1890.23: parse error, unexpected ":", expecting ";"
or "|"
../../src/gcc/java/parse.y:1892.3-1899.47: $3 of `catch_clause' has no declared
type
../../src/gcc/java/parse.y:1892.3-1901.46: $3 of `catch_clause' has no declared
type
../../src/gcc/java/parse.y:1892.3-1902.41: $3 of `catch_clause' has no declared
type
make[4]: *** [../../src/gcc/java/parse.c] Error 1
make[4]: Leaving directory `/tmp/buildd/gcc-3.0-3.0.4ds3/build/gcc'
make[3]: *** [stage1_build] Error 2
make[3]: Leaving directory `/tmp/buildd/gcc-3.0-3.0.4ds3/build/gcc'
make[2]: *** [bootstrap-lean] Error 2
make[2]: Leaving directory `/tmp/buildd/gcc-3.0-3.0.4ds3/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-3.0-3.0.4ds3'
make: *** [stamps/05-build-stamp] Error 2
===========================================
Full build log is available at:
http://www.netfort.gr.jp/~dancer/software/failed-log/gcc-3.0.log
regards,
junichi
---------------------------------------
Received: (at 172878-done) by bugs.debian.org; 11 Jan 2003 11:43:20 +0000
>From [EMAIL PROTECTED] Sat Jan 11 05:43:20 2003
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18XK2o-0000x4-00; Sat, 11 Jan 2003 05:43:18 -0600
Received: from bolero.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.19.1])
by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id MAA17605;
Sat, 11 Jan 2003 12:30:58 +0100 (MET)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.11.6+Sun/8.9.3) id h0BBUvG06119;
Sat, 11 Jan 2003 12:30:57 +0100 (MET)
From: Matthias Klose <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[EMAIL PROTECTED]>
Date: Sat, 11 Jan 2003 12:30:57 +0100
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: closing FTBFS reports for gcc-3.0
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=0.6 required=5.0
tests=SPAM_PHRASE_00_01
version=2.41
X-Spam-Level:
closing these reports:
- gcc-3.0 1:3.0.4ds3-14 does have the bison fixes (well, one is
missing for gcj, but gcj-3.0 isn't built anymore from this sources).
- the package now builds the libstdc++ runtime only. we cannot build
this on a glibc-2.3 based system (and the rules file does say this),
It's unlikely that someone makes a backport of the relevant parts.
So this is a "last" upload for gcc-3.0 to provide the libstdc++
runtime.
