Package: qpdf
Version: 2.0.2-1
User: [EMAIL PROTECTED]
Usertags: ftbfs-gcc-4.4
Tags: patch

Your package fails to build with the upcoming GCC 4.4.  Version 4.4
has not been released yet but I'm building with a snapshot in order
to find errors and give people an advance warning.

GCC 4.4 cleaned up some more C++ headers.  You always have to #include
headers directly and cannot rely for things to be included indirectly.

You can reproduce this problem with gcc-snapshot from unstable.

> Automatic build of qpdf_2.0.2-1 on em64t by sbuild/amd64 0.53
...
> /bin/sh ./libtool --quiet --mode=compile g++  -g -O2 -g -Wall -O2 -Wall 
> -Werror -MD -MF libqpdf/build/QPDF_Name.tdep -MP -Iinclude -Ilibqpdf -c 
> libqpdf/QPDF_Name.cc -o libqpdf/build/QPDF_Name.o; sed -e 's/\.o:/.lo:/' < 
> libqpdf/build/QPDF_Name.tdep > libqpdf/build/QPDF_Name.dep
> libqpdf/QPDF_Name.cc: In static member function 'static std::string 
> QPDF_Name::normalizeName(const std::string&)':
> libqpdf/QPDF_Name.cc:27: error: 'sprintf' was not declared in this scope

--- qpdf-2.0.2/libqpdf/QPDF_Name.cc~    2008-11-12 07:58:31.000000000 +0000
+++ qpdf-2.0.2/libqpdf/QPDF_Name.cc     2008-11-12 07:58:36.000000000 +0000
@@ -1,6 +1,7 @@
 
 #include <qpdf/QPDF_Name.hh>
 
+#include <cstdio>
 #include <string.h>
 
 QPDF_Name::QPDF_Name(std::string const& name) :
--- qpdf-2.0.2/libtests/bits.cc~        2008-11-12 08:00:38.000000000 +0000
+++ qpdf-2.0.2/libtests/bits.cc 2008-11-12 08:00:43.000000000 +0000
@@ -2,6 +2,7 @@
 #include <qpdf/BitStream.hh>
 #include <qpdf/BitWriter.hh>
 #include <qpdf/Pl_Buffer.hh>
+#include <cstdio>
 #include <iostream>
 
 // See comments in bits.cc
--- qpdf-2.0.2/libtests/md5.cc~ 2008-11-12 08:02:27.000000000 +0000
+++ qpdf-2.0.2/libtests/md5.cc  2008-11-12 08:02:32.000000000 +0000
@@ -2,6 +2,7 @@
 #include <qpdf/MD5.hh>
 #include <qpdf/Pl_MD5.hh>
 #include <qpdf/Pl_Discard.hh>
+#include <cstdio>
 #include <iostream>
 
 static void test_string(char const* str)

-- 
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