Bug#489386: diagnostics 0.2.2 FTBFS with g++-4.3 on s390

[Thomas Girard]

Please find attached the patch used for the NMU (without the autotools
part).

Regards,

Thomas

diff -Nru diagnostics-0.2.2/debian/changelog diagnostics-0.2.2+nmu1/debian/changelog
--- diagnostics-0.2.2/debian/changelog	2008-01-23 23:04:38.0 +0100
+++ diagnostics-0.2.2+nmu1/debian/changelog	2008-07-05 13:58:09.0 +0200
@@ -1,3 +1,11 @@
+diagnostics (0.2.2+nmu1) unstable; urgency=low
+
+  * Non-maintainer upload, as requested by Michael.
+  * Work-around a g++ 4.3 bug on s390 causing the package to FTBFS on this
+arch (closes: #489386)
+
+ -- Thomas Girard <[EMAIL PROTECTED]>  Sat, 05 Jul 2008 13:51:35 +0200
+
 diagnostics (0.2.2) unstable; urgency=low
 
   * stream_test_system.cpp: #include cstring to fix FTBFS with gcc 4.3
diff -Nru diagnostics-0.2.2/diagnostics/macros/invariance_annotation.t.cpp diagnostics-0.2.2+nmu1/diagnostics/macros/invariance_annotation.t.cpp
--- diagnostics-0.2.2/diagnostics/macros/invariance_annotation.t.cpp	2007-03-01 22:43:26.0 +0100
+++ diagnostics-0.2.2+nmu1/diagnostics/macros/invariance_annotation.t.cpp	2008-07-05 13:59:31.0 +0200
@@ -157,7 +157,7 @@
 private:
 mutable int m_class_invariance_called;
 
-bool m_throw;
+volatile bool m_throw;
 };
 
 

Bug#489386: diagnostics 0.2.2 FTBFS with g++-4.3 on s390

[Thomas Girard]

Package: diagnostics
Version: 0.2.2
Severity: serious
Justification: no longer builds from source

a binary NMU rebuild of diagnostics shows diagnostics FTBFS on s390[1].
A NMU will follow, as requested by the maintainer.

Regards,

Thomas

[1] 
http://buildd.debian.org/fetch.cgi?pkg=diagnostics;ver=0.2.2%2Bb1;arch=s390;stamp=1214648343

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.25micmac (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash




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