Your message dated Mon, 17 Jan 2005 08:05:05 +0100
with message-id <[EMAIL PROTECTED]>
and subject line fixed in gcc-4.0_4.0ds3-0pre4 upload
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; 24 Sep 2004 10:40:11 +0000
>From [EMAIL PROTECTED] Fri Sep 24 03:40:11 2004
Return-path: <[EMAIL PROTECTED]>
Received: from lilly.ping.de [83.97.42.2]
by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
id 1CAnUp-0003Lz-00; Fri, 24 Sep 2004 03:40:11 -0700
Received: (qmail 8277 invoked by uid 10); 24 Sep 2004 10:40:07 -0000
Received: from vorlon.ping.de by lilly.ping.de with BSMTP (rgsmtp-qm-ot 0.6)
for <[EMAIL PROTECTED]>; 24 Sep 2004 10:40:07 -0000
Received: from michael by vorlon.ping.de with local (Exim 4.34)
id 1CAnPr-000126-NO
for [EMAIL PROTECTED]; Fri, 24 Sep 2004 12:35:03 +0200
Date: Fri, 24 Sep 2004 12:35:03 +0200
From: Michael Bienia <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: gcc-4.0: Doesn't build on amd64 (pure64/gcc-3.4)
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Reportbug-Version: 2.99.3
User-Agent: Mutt/1.5.6+20040818i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(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_2004_03_25
X-Spam-Level:
Package: gcc-4.0
Version: 4.0-0pre0
Severity: normal
Tags: experimental
Hello,
I tried to build gcc-4.0 on my amd64-box running pure64/gcc-3.4 but it
failed with the following error message (copied from
bootstrap-protocol):
/home/gcc4/gcc-4.0-4.0/build/gcc/xgcc -shared-libgcc
-B/home/gcc4/gcc-4.0-4.0/build/gcc/ -nostdinc++
-L/home/gcc4/gcc-4.0-4.0/build/x86_64-linux/libstdc++-v3/src
-L/home/gcc4/gcc-4.0-4.0/build/x86_64-linux/libstdc++-v3/src/.libs
-B/usr/x86_64-linux/bin/ -B/usr/x86_64-linux/lib/ -isystem
/usr/x86_64-linux/include -isystem /usr/x86_64-linux/sys-include
-I/home/gcc4/gcc-4.0-4.0/src/libstdc++-v3/../gcc
-I/home/gcc4/gcc-4.0-4.0/build/x86_64-linux/libstdc++-v3/include/x86_64-linux
-I/home/gcc4/gcc-4.0-4.0/build/x86_64-linux/libstdc++-v3/include
-I/home/gcc4/gcc-4.0-4.0/src/libstdc++-v3/libsupc++ -O2 -g -O2 -g -O2
-D_GNU_SOURCE -fno-implicit-templates -Wall -Wextra -Wwrite-strings
-Wcast-qual -fdiagnostics-show-location=once -ffunction-sections
-fdata-sections -c ../../../../src/libstdc++-v3/libsupc++/guard.cc
-fPIC -DPIC -o guard.o
../../../../src/libstdc++-v3/libsupc++/guard.cc:62: error: expected
primary-expression before '.' token
../../../../src/libstdc++-v3/libsupc++/guard.cc:62: error: expected
primary-expression before '{' token
../../../../src/libstdc++-v3/libsupc++/guard.cc:62: error: expected `}' before
'{' token
../../../../src/libstdc++-v3/libsupc++/guard.cc:62: error: expected `,' or `;'
before '{' token
../../../../src/libstdc++-v3/libsupc++/guard.cc:86: error: expected declaration
before '}' token
../../../../src/libstdc++-v3/libsupc++/guard.cc:40:1: unterminated #ifdef
make[6]: *** [guard.lo] Error 1
make[6]: Leaving directory
`/home/gcc4/gcc-4.0-4.0/build/x86_64-linux/libstdc++-v3/libsupc++'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory
`/home/gcc4/gcc-4.0-4.0/build/x86_64-linux/libstdc++-v3'
make[4]: *** [all] Error 2
make[4]: Leaving directory
`/home/gcc4/gcc-4.0-4.0/build/x86_64-linux/libstdc++-v3'
make[3]: *** [all-target-libstdc++-v3] Error 2
make[3]: Leaving directory `/home/gcc4/gcc-4.0-4.0/build'
make[2]: *** [bootstrap] Error 2
make[2]: Leaving directory `/home/gcc4/gcc-4.0-4.0/build'
I tried to build it in a chroot which I normally use to build gnome 2.8
packages. The directory with the failed build does still exist, so if
you need some more information let me know.
Michael
-- System Information:
Debian Release: 3.1
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.9-rc2-bk5
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8
---------------------------------------
Received: (at 273159-done) by bugs.debian.org; 17 Jan 2005 07:05:22 +0000
>From [EMAIL PROTECTED] Sun Jan 16 23:05:22 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CqQwz-0006zt-00; Sun, 16 Jan 2005 23:05:21 -0800
Received: from mailhost.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.17.13])
by mail.cs.tu-berlin.de (8.9.3p2/8.9.3) with ESMTP id IAA10938;
Mon, 17 Jan 2005 08:05:16 +0100 (MET)
Received: from localhost (localhost [127.0.0.1])
by mailhost.cs.tu-berlin.de (Postfix) with ESMTP id 2C388F216;
Mon, 17 Jan 2005 08:05:16 +0100 (MET)
Received: from mailhost.cs.tu-berlin.de ([127.0.0.1])
by localhost (bueno [127.0.0.1]) (amavisd-new, port 10224) with ESMTP
id 28648-09; Mon, 17 Jan 2005 08:05:05 +0100 (MET)
Received: from bolero.cs.tu-berlin.de (bolero.cs.tu-berlin.de [130.149.19.1])
by mailhost.cs.tu-berlin.de (Postfix) with ESMTP;
Mon, 17 Jan 2005 08:05:05 +0100 (MET)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id j0H755hQ025605;
Mon, 17 Jan 2005 08:05:05 +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: Mon, 17 Jan 2005 08:05:05 +0100
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: fixed in gcc-4.0_4.0ds3-0pre4 upload
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
X-Virus-Scanned: by amavisd-new at cs.tu-berlin.de
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=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
X-CrossAssassin-Score: 4
these issues are fixed in the gcc-4.0_4.0ds3-0pre4 upload to
experimental. Built for i386, ia64, sparc and powerpc.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
