Your message dated Sat, 27 Mar 2004 12:18:05 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#236291: Processed: reassigning to gcc-3.3
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; 5 Mar 2004 12:39:48 +0000
>From [EMAIL PROTECTED] Fri Mar 05 04:39:48 2004
Return-path: <[EMAIL PROTECTED]>
Received: from moutng.kundenserver.de [212.227.126.173]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AzEcG-0004B7-00; Fri, 05 Mar 2004 04:39:48 -0800
Received: from [212.227.126.205] (helo=mrelayng.kundenserver.de)
by moutng.kundenserver.de with esmtp (Exim 3.35 #1)
id 1AzEcF-0001zp-00
for [EMAIL PROTECTED]; Fri, 05 Mar 2004 13:39:47 +0100
Received: from [62.109.112.76] (helo=jwsdot.com)
by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1)
id 1AzEcF-0003vr-00
for [EMAIL PROTECTED]; Fri, 05 Mar 2004 13:39:47 +0100
Message-ID: <[EMAIL PROTECTED]>
Date: Fri, 05 Mar 2004 13:39:30 +0100
From: Alexander Sack <[EMAIL PROTECTED]>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040227)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: [EMAIL PROTECTED]
Subject: FTBFS on hppa architecture
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: kundenserver.de [EMAIL PROTECTED]
auth:cbe77bd78e1b43e9d8afa4235a070258
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_05
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no
version=2.60-bugs.debian.org_2004_03_05
X-Spam-Level:
Package: mozilla-thunderbird
Version: 0.5-3
Severity: serious
Tags: sid
The current version FTBFS on hppa (See:
http://buildd.debian.org/build.php?&pkg=mozilla-thunderbird&ver=0.5-3&arch=hppa&file=log)
---------------------------------------
Received: (at 236291-done) by bugs.debian.org; 27 Mar 2004 11:18:38 +0000
>From [EMAIL PROTECTED] Sat Mar 27 03:18:38 2004
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 1B7Bpm-0005A5-00; Sat, 27 Mar 2004 03:18:38 -0800
Received: from bolero.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.19.1])
by mail.cs.tu-berlin.de (8.9.3p2/8.9.3) with ESMTP id MAA27391;
Sat, 27 Mar 2004 12:18:06 +0100 (MET)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id i2RBI5Wr029012;
Sat, 27 Mar 2004 12:18: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: Sat, 27 Mar 2004 12:18:05 +0100
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Cc: Falk Hueffner <[EMAIL PROTECTED]>
Subject: Re: Bug#236291: Processed: reassigning to gcc-3.3
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
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=-5.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Alexander Sack writes:
> Hi Falk,
>
> I am sorry, but I can't! If you take a look at the bug report (second or
> third posting) you will find the .c file whose compilation apparently
> (gcc-3.3 -c ) segfaults on the buildd hppa box.
this failure was only seen on a buildd, which is now upgraded to a
recent gcc-3.3.
