Your message dated Thu, 6 Oct 2005 09:36:01 +0200
with message-id <[EMAIL PROTECTED]>
and subject line fixed: libcrypto++: FTBFS on arm, m68k, hppa; use g++-3.4 there
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; 6 Oct 2005 07:36:32 +0000
>From [EMAIL PROTECTED] Thu Oct 06 00:36:32 2005
Return-path: <[EMAIL PROTECTED]>
Received: from qproxy.gmail.com [72.14.204.196]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1ENQIq-00037I-00; Thu, 06 Oct 2005 00:36:32 -0700
Received: by qproxy.gmail.com with SMTP id a10so286042qbd
for <[EMAIL PROTECTED]>; Thu, 06 Oct 2005 00:36:01 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail.com;
h=received:message-id:date:from:reply-to:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
b=Tsmr5Ai9jCIKHf8GH44hMd/N4SzBQHmTcZ55WhhfGmmUXpeb5y6cJm0BQK+nifK9BXAQ1Ge/Gg3+es4HzpGUFWwO0c7ASesrAd/YgrXQ83+EVN71eGMULZ9pfdmUJYAZnkcFug+K4ZjWR5c962lzfM9GMee9nqboapVKScA2bEk=
Received: by 10.64.195.16 with SMTP id s16mr176900qbf;
Thu, 06 Oct 2005 00:36:01 -0700 (PDT)
Received: by 10.65.35.14 with HTTP; Thu, 6 Oct 2005 00:36:01 -0700 (PDT)
Message-ID: <[EMAIL PROTECTED]>
Date: Thu, 6 Oct 2005 09:36:01 +0200
From: Jens Peter Secher <[EMAIL PROTECTED]>
Reply-To: Jens Peter Secher <[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: fixed: libcrypto++: FTBFS on arm, m68k, hppa; use g++-3.4 there
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
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=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
libcrypto5.2c2 now builds on all architectures.
--
Jens Peter Secher
_DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
