Your message dated Thu, 22 Sep 2005 13:48:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#328975: fixed in libcrypto++ 5.2.1c2-6
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; 18 Sep 2005 14:21:00 +0000
>From [EMAIL PROTECTED] Sun Sep 18 07:21:00 2005
Return-path: <[EMAIL PROTECTED]>
Received: from 84-120-66-144.onocable.ono.com (chistera.yi.org) [84.120.66.144] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EH02N-0006bD-00; Sun, 18 Sep 2005 07:20:59 -0700
Received: from userid 1000 by chistera.yi.org with local (Exim 4.52) 
          id 1EH02L-0000t3-L7
          for [EMAIL PROTECTED]; Sun, 18 Sep 2005 16:20:57 +0200
Date: Sun, 18 Sep 2005 16:20:57 +0200
From: Adeodato =?utf-8?B?U2ltw7M=?= <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: libcrypto++: FTBFS on arm, m68k, hppa; use g++-3.4 there
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="fUYQa+Pmc3FrFX/N"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-No-CC: Please respect my Mail-Followup-To header
User-Agent: Mutt/1.5.10i
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.8 required=4.0 tests=BAYES_00,FROM_ENDS_IN_NUMS,
        HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02


--fUYQa+Pmc3FrFX/N
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

Package: libcrypto++
Version: 5.2.1c2-5
Severity: serious
Tags: patch

Hello,

  libcrypto++ FTBFS on arm, m68k and hppa due to GCC 4 giving an
  Internal Compiler Error there. Using -O1 or -O0 does not help, so the
  workaround is to compile with g++-3.4 on those architectures (this is
  possible because the C++ ABIs of 3.4 and 4.0 are compatible).

  A patch is attached (build tested on paer). If needed, I can upload
  myself.

  Cheers,

-- 
Adeodato Simó
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
    Listening to: Ana Belén - Peces de ciudad
 
A lie can go round the world before the truth has got its boots on.
                -- Terry Pratchett

--fUYQa+Pmc3FrFX/N
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="libcrypto++-gcc3.4.diff"

diff -u -rua libcrypto++-5.2.1c2.orig/debian/control 
libcrypto++-5.2.1c2/debian/control
--- libcrypto++-5.2.1c2.orig/debian/control     2005-09-18 16:14:31.000000000 
+0200
+++ libcrypto++-5.2.1c2/debian/control  2005-09-18 16:14:16.000000000 +0200
@@ -4,7 +4,7 @@
 Maintainer: Jens Peter Secher <[EMAIL PROTECTED]>
 Uploaders: Pierre Machard <[EMAIL PROTECTED]>
 Standards-Version: 3.6.2
-Build-Depends: debhelper (>= 4), automake1.9, autoconf, libtool, dpatch
+Build-Depends: g++-3.4 [arm m68k hppa], debhelper (>= 4), automake1.9, 
autoconf, libtool, dpatch
 Build-Depends-Indep: doxygen
 
 Package: libcrypto++5.2c2
diff -u -rua libcrypto++-5.2.1c2.orig/debian/rules 
libcrypto++-5.2.1c2/debian/rules
--- libcrypto++-5.2.1c2.orig/debian/rules       2005-09-18 16:14:31.000000000 
+0200
+++ libcrypto++-5.2.1c2/debian/rules    2005-09-18 16:14:13.000000000 +0200
@@ -36,6 +36,16 @@
        cflags += -ffunction-sections
 endif
 
+# gcc4 ICEs on some arches
+GCC4_ICES_HERE := arm m68k hppa
+DEB_HOST_ARCH_CPU ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_CPU)
+
+ifneq (,$(filter $(DEB_HOST_ARCH_CPU),$(GCC4_ICES_HERE)))
+    export CC=gcc-3.4
+    export CPP=cpp-3.4
+    export CXX=g++-3.4
+endif
+
 autotools_input := configure.ac Makefile.am config.h.in
 
 autoclean:

--fUYQa+Pmc3FrFX/N--


---------------------------------------
Received: (at 328975-close) by bugs.debian.org; 22 Sep 2005 20:50:48 +0000
>From [EMAIL PROTECTED] Thu Sep 22 13:50:48 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1EIXzC-0001mm-00; Thu, 22 Sep 2005 13:48:06 -0700
From: Jens Peter Secher <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#328975: fixed in libcrypto++ 5.2.1c2-6
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 22 Sep 2005 13:48:06 -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

Source: libcrypto++
Source-Version: 5.2.1c2-6

We believe that the bug you reported is fixed in the latest version of
libcrypto++, which is due to be installed in the Debian FTP archive:

libcrypto++-dev_5.2.1c2-6_i386.deb
  to pool/main/libc/libcrypto++/libcrypto++-dev_5.2.1c2-6_i386.deb
libcrypto++-doc_5.2.1c2-6_all.deb
  to pool/main/libc/libcrypto++/libcrypto++-doc_5.2.1c2-6_all.deb
libcrypto++-utils_5.2.1c2-6_i386.deb
  to pool/main/libc/libcrypto++/libcrypto++-utils_5.2.1c2-6_i386.deb
libcrypto++5.2c2_5.2.1c2-6_i386.deb
  to pool/main/libc/libcrypto++/libcrypto++5.2c2_5.2.1c2-6_i386.deb
libcrypto++_5.2.1c2-6.diff.gz
  to pool/main/libc/libcrypto++/libcrypto++_5.2.1c2-6.diff.gz
libcrypto++_5.2.1c2-6.dsc
  to pool/main/libc/libcrypto++/libcrypto++_5.2.1c2-6.dsc



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.
Jens Peter Secher <[EMAIL PROTECTED]> (supplier of updated libcrypto++ 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: Tue, 20 Sep 2005 20:46:29 +0200
Source: libcrypto++
Binary: libcrypto++-utils libcrypto++-doc libcrypto++-dev libcrypto++5.2c2
Architecture: source all i386
Version: 5.2.1c2-6
Distribution: unstable
Urgency: low
Maintainer: Jens Peter Secher <[EMAIL PROTECTED]>
Changed-By: Jens Peter Secher <[EMAIL PROTECTED]>
Description: 
 libcrypto++-dev - General purpose cryptographic C++ library - development
 libcrypto++-doc - General purpose cryptographic library - documentation
 libcrypto++-utils - General purpose cryptographic library - utilities and data 
files
 libcrypto++5.2c2 - General purpose cryptographic shared library
Closes: 328975
Changes: 
 libcrypto++ (5.2.1c2-6) unstable; urgency=low
 .
   * Circumvent GCC4 internal compiler error on m68k, arm, and hppa by
     using GCC3.4 on those architectures, thanks to Adeodato Simó
     (Closes: #328975).
Files: 
 81a860b82cae47874d36f8ccef0978d1 781 libs optional libcrypto++_5.2.1c2-6.dsc
 fb987fd80e690912af31829705e3b9b1 21671 libs optional 
libcrypto++_5.2.1c2-6.diff.gz
 5f4f9178416af379a98b36e5aa2dc785 5296170 doc optional 
libcrypto++-doc_5.2.1c2-6_all.deb
 ee0902fda6d38ddf18d1b369bf605ea5 1314448 libs optional 
libcrypto++5.2c2_5.2.1c2-6_i386.deb
 59826f395df87d37a6549caebe8cfe9a 3149606 libdevel optional 
libcrypto++-dev_5.2.1c2-6_i386.deb
 2169e6385d408edbe52fd1b4efd71dbb 922754 utils optional 
libcrypto++-utils_5.2.1c2-6_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDMaynDuWXiv5j6KERAkTWAJ47JW15aVmTNe00vsumdf21mAHscACfVj4s
FhfgV6Uo0jUJLeh0pHrJSFk=
=rB1P
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to