Your message dated Fri, 23 Dec 2005 14:42:50 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in 5.1-4
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; 21 Dec 2005 02:13:30 +0000
>From [EMAIL PROTECTED] Tue Dec 20 18:13:30 2005
Return-path: <[EMAIL PROTECTED]>
Received: from ms-smtp-04.nyroc.rr.com ([24.24.2.58])
by spohr.debian.org with esmtp (Exim 4.50)
id 1EotTu-0007vu-Jz
for [EMAIL PROTECTED]; Tue, 20 Dec 2005 18:13:30 -0800
Received: from doctormoo (cpe-24-59-102-234.twcny.res.rr.com [24.59.102.234])
by ms-smtp-04.nyroc.rr.com (8.12.10/8.12.10) with ESMTP id
jBL2DRRD016748;
Tue, 20 Dec 2005 21:13:28 -0500 (EST)
Received: from neroden by doctormoo with local (Exim 4.60)
(envelope-from <[EMAIL PROTECTED]>)
id 1EotTr-0003Ja-Lt; Tue, 20 Dec 2005 21:13:27 -0500
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Nathanael Nerode <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: readline5: FTBFS on i386, s390, powerpc.
Message-ID: <[EMAIL PROTECTED]>
X-Mailer: reportbug 3.18
Date: Tue, 20 Dec 2005 21:13:27 -0500
X-Virus-Scanned: Symantec AntiVirus Scan Engine
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-Level:
X-Spam-Status: No, hits=-7.5 required=4.0 tests=BAYES_00,HAS_PACKAGE,
RCVD_IN_SORBS autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: readline5
Severity: serious
>From the buildd logs:
checking for C compiler default output file name... configure: error: C
compiler cannot create executables
The common factor in the three logs is that it dies in the "build64" part
of the build, which isn't present for the other architectures. The test
which is failing tries to compile and link a C file. Are you
perhaps missing some Build-Depends, so that configure can't find the 64-bit
GCC/system libraries to link with?
This breakage in libreadline5 is beginning to hold up movement of the c2a
transition into testing. If you can't get the build64 business working
soon I suggest disabling it for now.
---------------------------------------
Received: (at 344237-done) by bugs.debian.org; 23 Dec 2005 19:42:53 +0000
>From [EMAIL PROTECTED] Fri Dec 23 11:42:53 2005
Return-path: <[EMAIL PROTECTED]>
Received: from ms-smtp-01.nyroc.rr.com ([24.24.2.55])
by spohr.debian.org with esmtp (Exim 4.50)
id 1EpsoX-0001L7-0E
for [EMAIL PROTECTED]; Fri, 23 Dec 2005 11:42:53 -0800
Received: from doctormoo (cpe-24-59-103-207.twcny.res.rr.com [24.59.103.207])
by ms-smtp-01.nyroc.rr.com (8.12.10/8.12.10) with ESMTP id
jBNJgoFe013134
for <[EMAIL PROTECTED]>; Fri, 23 Dec 2005 14:42:50 -0500 (EST)
Received: from neroden by doctormoo with local (Exim 4.60)
(envelope-from <[EMAIL PROTECTED]>)
id 1EpsoU-0001fw-2f
for [EMAIL PROTECTED]; Fri, 23 Dec 2005 14:42:50 -0500
Date: Fri, 23 Dec 2005 14:42:50 -0500
To: [EMAIL PROTECTED]
Subject: Fixed in 5.1-4
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.11
From: Nathanael Nerode <[EMAIL PROTECTED]>
X-Virus-Scanned: Symantec AntiVirus Scan Engine
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-Level:
X-Spam-Status: No, hits=-2.5 required=4.0 tests=BAYES_00,RCVD_IN_SORBS
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Hooray.
--
Nathanael Nerode <[EMAIL PROTECTED]>
This space intentionally left blank.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
