Package: opensaml
Version: 1.1a-3
Usertags: ftbfs-gcc-4.3
Tags: patch

Your package fails to build with GCC 4.3.  Version 4.3 has not been
released yet but I'm building with a snapshot in order to find errors
and give people an advance warning.  In GCC 4.3, the C++ header
dependencies have been cleaned up.  The advantage of this is that
programs will compile faster.  The downside is that you actually
need to directly #include everything you use (but you really should
do this anyway, otherwise your program won't work with any compiler
other than GCC).

Apologies for filing yet another bug.  I thought the header clean-ups
were done but then some more changes happened.  I hope it's really
over now.

You can reproduce this problem with gcc-snapshot (20070422-1 or higher)
from unstable. (Currently not available for i386, but for amd64 and
and ia64.  I hope to have i386 binaries in the archive in the near
future.)

> Automatic build of opensaml_1.1a-3 on coconut0 by sbuild/ia64 0.49
...
>  g++ -DHAVE_CONFIG_H -I. -I. -I.. -I. -pthread -O2 -DNDEBUG -MT 
> SAMLException.lo -MD -MP -MF .deps/SAMLException.Tpo -c SAMLException.cpp  
> -fPIC -DPIC -o .libs/SAMLException.o
> SAMLException.cpp: In member function 'virtual xercesc_2_7::DOMNode* 
> saml::SAMLException::toDOM(xercesc_2_7::DOMDocument*, bool) const':
> SAMLException.cpp:518: error: must #include <typeinfo> before using typeid
> SAMLException.cpp:518: error: must #include <typeinfo> before using typeid
> SAMLException.cpp:525: error: must #include <typeinfo> before using typeid
> SAMLException.cpp:525: error: must #include <typeinfo> before using typeid
> make[4]: *** [SAMLException.lo] Error 1

--- saml/SAMLException.cpp~     2007-04-26 16:27:45.000000000 +0000
+++ saml/SAMLException.cpp      2007-04-26 16:28:02.000000000 +0000
@@ -23,6 +23,7 @@
 */
 
 #include "internal.h"
+#include <typeinfo>
 
 using namespace saml;
 using namespace std;

-- 
Martin Michlmayr
http://www.cyrius.com/


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

Reply via email to