Package: dvgrab
Version: 3.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 dvgrab_3.2-1 on em64t by sbuild/amd64 0.53
...
> mv -f .deps/dvgrab.Tpo .deps/dvgrab.Po
> g++ -DHAVE_CONFIG_H -I. -I/usr/include/lqt     -D_REENTRANT 
> -D_FILE_OFFSET_BITS=64 -Wall -O2 -MT error.o -MD -MP -MF .deps/error.Tpo -c 
> -o error.o error.cc
> error.cc: In function 'void sendEventParams(int, int, const char*, ...)':
> error.cc:84: error: 'stderr' was not declared in this scope
> error.cc:84: error: 'fprintf' was not declared in this scope
> error.cc:86: error: 'stderr' was not declared in this scope
> error.cc:86: error: 'fprintf' was not declared in this scope
> error.cc:90: error: 'snprintf' was not declared in this scope
> error.cc:92: error: 'snprintf' was not declared in this scope
> error.cc:95: error: 'stderr' was not declared in this scope
> error.cc:95: error: 'vfprintf' was not declared in this scope
> make[1]: *** [error.o] Error 1
> make[1]: Leaving directory `/build/tbm/dvgrab-3.2'
> make: *** [build-stamp] Error 2

--- error.cc~   2008-11-13 18:46:36.000000000 +0000
+++ error.cc    2008-11-13 18:46:44.000000000 +0000
@@ -28,6 +28,7 @@
 
 // C++ includes
 
+#include <cstdio>
 #include <string>
 #include <iostream>
 #include <sstream>
--- smiltime.cc~        2008-11-13 18:47:39.000000000 +0000
+++ smiltime.cc 2008-11-13 18:47:47.000000000 +0000
@@ -24,6 +24,7 @@
 
 #include "smiltime.h"
 
+#include <cstdio>
 #include <iostream>
 #include <iomanip>
 #include <sstream>

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