Your message dated Tue, 02 Aug 2005 08:47:04 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#307503: fixed in libatomic-ops 1.0-1
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; 3 May 2005 16:27:57 +0000
>From [EMAIL PROTECTED] Tue May 03 09:27:57 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 1DT0FZ-0008LZ-00; Tue, 03 May 2005 09:27:57 -0700
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 SAA13268
for <[EMAIL PROTECTED]>; Tue, 3 May 2005 18:27:52 +0200 (MEST)
Received: from localhost (localhost [127.0.0.1])
by mailhost.cs.tu-berlin.de (Postfix) with ESMTP id 1FF42F21E
for <[EMAIL PROTECTED]>; Tue, 3 May 2005 18:27:52 +0200 (MEST)
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 01122-17 for <[EMAIL PROTECTED]>;
Tue, 3 May 2005 18:27:51 +0200 (MEST) 13923
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
for <[EMAIL PROTECTED]>; Tue, 3 May 2005 18:27:51 +0200 (MEST)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id j43GRp2Q007887;
Tue, 3 May 2005 18:27:51 +0200 (MEST)
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: Tue, 3 May 2005 18:27:51 +0200
To: [EMAIL PROTECTED]
Subject: FTBFS using gcc-4.0
X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" 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=-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: libunwind
Version: 0.98.5
gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I../include -I../include/ia64
-I../include -I. -D_GNU_SOURCE -DNDEBUG -g -O2 -Wall -Wsign-compare
-MT mi/mempool.lo -MD -MP -MF mi/.deps/mempool.Tpo -c mi/mempool.c
-fPIC -DPIC -o mi/.libs/mempool.o
mi/mempool.c: In function '_UIia64__sos_alloc':
/usr/include/atomic_ops/sysdeps/gcc/ia64.h:99: error: impossible
constraint in 'asm'
/usr/include/atomic_ops/sysdeps/gcc/ia64.h:99: error: impossible
constraint in 'asm'
make[3]: *** [mi/mempool.lo] Error 1
---------------------------------------
Received: (at 307503-close) by bugs.debian.org; 2 Aug 2005 15:53:20 +0000
>From [EMAIL PROTECTED] Tue Aug 02 08:53:20 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
id 1Dzyyu-0005i4-00; Tue, 02 Aug 2005 08:47:04 -0700
From: Al Stone <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#307503: fixed in libatomic-ops 1.0-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Tue, 02 Aug 2005 08:47:04 -0700
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=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 2
Source: libatomic-ops
Source-Version: 1.0-1
We believe that the bug you reported is fixed in the latest version of
libatomic-ops, which is due to be installed in the Debian FTP archive:
libatomic-ops-dev_1.0-1_i386.deb
to pool/main/liba/libatomic-ops/libatomic-ops-dev_1.0-1_i386.deb
libatomic-ops_1.0-1.dsc
to pool/main/liba/libatomic-ops/libatomic-ops_1.0-1.dsc
libatomic-ops_1.0-1.tar.gz
to pool/main/liba/libatomic-ops/libatomic-ops_1.0-1.tar.gz
libatomic-ops_1.0-1_i386.deb
to pool/main/liba/libatomic-ops/libatomic-ops_1.0-1_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Al Stone <[EMAIL PROTECTED]> (supplier of updated libatomic-ops package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Mon, 1 Aug 2005 22:25:38 -0600
Source: libatomic-ops
Binary: libatomic-ops libatomic-ops-dev
Architecture: source i386
Version: 1.0-1
Distribution: unstable
Urgency: low
Maintainer: Ian Wienand <[EMAIL PROTECTED]>
Changed-By: Al Stone <[EMAIL PROTECTED]>
Description:
libatomic-ops - A library for atomic operations (static library only)
libatomic-ops-dev - A library for atomic operations (development files)
Closes: 307448 307503
Changes:
libatomic-ops (1.0-1) unstable; urgency=low
.
* Closes: bug#307503 -- FTBS. Update to upstream 1.0 (ianw)
* The 'libatomic-ops' package now contains only a statically linked
library, as upstream wishes (which makes sense, in this case, and
still fits within policy). The 'libatomic-ops-dev' package now
depends on the 'libatomic-ops' as a result to ensure a developer
can still properly link against the package (ahs3).
* Update standards version to 3.6.2 (ahs3)
* Closes: bug#307448 -- variable 'ret' undefined on ARM. I think
this has been solved but I could be wrong and may have to reopen
this bug (ahs3).
Files:
5432bf46e753689719efa11a9aa66713 570 - optional libatomic-ops_1.0-1.dsc
633d54f3150318b628a8c6fca47f87fa 188439 - optional libatomic-ops_1.0-1.tar.gz
50844ada2d2cb66fd6a53f5e932ba746 9576 libdevel optional
libatomic-ops_1.0-1_i386.deb
ca8931f7670d1c2dbf4aacbdbdb2ada1 45382 libdevel optional
libatomic-ops-dev_1.0-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC7v/4so6+T7qY4V0RAvboAJ46NKVberknyKs8wKFmyWLznWBSvgCfbMJ2
nROYdKcbd29dQPhsD6foibc=
=sfGx
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
