Your message dated Fri, 11 Dec 2009 18:34:15 +0000
with message-id <e1njajj-0004ut...@ries.debian.org>
and subject line Bug#505024: fixed in wpg2odg 0.1.0-4
has caused the Debian Bug report #505024,
regarding FTBFS with GCC 4.4: missing #include
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
505024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wpg2odg
Version: 0.1.0-3
User: debian-...@lists.debian.org
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 wpg2odg_0.1.0-3 on em64t by sbuild/amd64 0.53
...
> if x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I..    
> -I/usr/include/libwpg-0.1 -I/usr/include/libwpd-0.8   -DNDEBUG -I../filter  
> -g -O2 -MT StdOutputHandler.o -MD -MP -MF ".deps/StdOutputHandler.Tpo" -c -o 
> StdOutputHandler.o StdOutputHandler.cxx; \
>       then mv -f ".deps/StdOutputHandler.Tpo" ".deps/StdOutputHandler.Po"; 
> else rm -f ".deps/StdOutputHandler.Tpo"; exit 1; fi
> StdOutputHandler.cxx: In member function 'virtual void 
> StdOutputHandler::startElement(const char*, const 
> std::vector<std::pair<std::basic_string<char, std::char_traits<char>, 
> std::allocator<char> >, std::basic_string<char, std::char_traits<char>, 
> std::allocator<char> > >, std::allocator<std::pair<std::basic_string<char, 
> std::char_traits<char>, std::allocator<char> >, std::basic_string<char, 
> std::char_traits<char>, std::allocator<char> > > > >&)':
> StdOutputHandler.cxx:41: error: 'printf' was not declared in this scope
> StdOutputHandler.cxx:44: error: 'printf' was not declared in this scope
> StdOutputHandler.cxx: In member function 'virtual void 
> StdOutputHandler::endElement(const char*)':
> StdOutputHandler.cxx:59: error: 'printf' was not declared in this scope
> StdOutputHandler.cxx:64: error: 'printf' was not declared in this scope
> StdOutputHandler.cxx:71: error: 'printf' was not declared in this scope
> StdOutputHandler.cxx: In member function 'virtual void 
> StdOutputHandler::characters(const std::string&)':
> StdOutputHandler.cxx:80: error: 'printf' was not declared in this scope
> StdOutputHandler.cxx:83: error: 'printf' was not declared in this scope
> StdOutputHandler.cxx: In member function 'virtual void 
> StdOutputHandler::endDocument()':
> StdOutputHandler.cxx:90: error: 'printf' was not declared in this scope
> make[3]: *** [StdOutputHandler.o] Error 1
> make[3]: Leaving directory `/build/tbm/wpg2odg-0.1.0/cmdline'
> make[2]: *** [all-recursive] Error 1

--- cmdline/StdOutputHandler.cxx~       2008-11-08 17:05:05.000000000 +0000
+++ cmdline/StdOutputHandler.cxx        2008-11-08 17:05:11.000000000 +0000
@@ -24,6 +24,7 @@
  */
 
 #include "StdOutputHandler.hxx"
+#include <cstdio>
 
 StdOutputHandler::StdOutputHandler() :
        mbIsTagOpened(false)

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



--- End Message ---
--- Begin Message ---
Source: wpg2odg
Source-Version: 0.1.0-4

We believe that the bug you reported is fixed in the latest version of
wpg2odg, which is due to be installed in the Debian FTP archive:

wpg2odg_0.1.0-4.diff.gz
  to main/w/wpg2odg/wpg2odg_0.1.0-4.diff.gz
wpg2odg_0.1.0-4.dsc
  to main/w/wpg2odg/wpg2odg_0.1.0-4.dsc
wpg2odg_0.1.0-4_amd64.deb
  to main/w/wpg2odg/wpg2odg_0.1.0-4_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 505...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rene Engelhard <r...@debian.org> (supplier of updated wpg2odg package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 11 Dec 2009 19:12:28 +0100
Source: wpg2odg
Binary: wpg2odg
Architecture: source amd64
Version: 0.1.0-4
Distribution: unstable
Urgency: low
Maintainer: Rene Engelhard <r...@debian.org>
Changed-By: Rene Engelhard <r...@debian.org>
Description: 
 wpg2odg    - WPG to ODG converter
Closes: 505024
Changes: 
 wpg2odg (0.1.0-4) unstable; urgency=low
 .
   * add 01_gcc44 to add missing includes with gcc 4.4 (closes: #505024)
Checksums-Sha1: 
 0b98221f2f2330329f2cdceb160b5f4073a1da48 1641 wpg2odg_0.1.0-4.dsc
 9b0eeb8fa75f4bf6b370068dd0a099c663ddea97 3460 wpg2odg_0.1.0-4.diff.gz
 c8fb64a607a164a1d83f7c4471f4d6818a47f66a 40818 wpg2odg_0.1.0-4_amd64.deb
Checksums-Sha256: 
 5edb7a40e94908a9adcc69239f2343c9e122afcccd686d9fa9a769fcf2ceec00 1641 
wpg2odg_0.1.0-4.dsc
 5afa84625e4272100530f0917b918ac234e0e33a63fbf11f64b69b7aaa504055 3460 
wpg2odg_0.1.0-4.diff.gz
 6425acb9125074758ea9b4425db2093254df1ce948f801c83677d2d45907af93 40818 
wpg2odg_0.1.0-4_amd64.deb
Files: 
 c9c5f1e4f452be9494a40ace7d833702 1641 utils optional wpg2odg_0.1.0-4.dsc
 ae17ad374c56bf366fecf864a117a593 3460 utils optional wpg2odg_0.1.0-4.diff.gz
 e8f68b369be3710d1bedb6106969d8da 40818 utils optional wpg2odg_0.1.0-4_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJLIov3AAoJEAqgRXHQPj5wfBkP/RFWKEo9/5azCerE3WeIPbAq
tcyDsRGzK5grRCUJ6DWNafzn1Wg5alq342kCwtYe4mekSOXD1vfaNl4nRUTqde9M
fD6JvS9J7Yzu3iCkKu6yo/F1WWP6JXb2sfOfig6WST81JkSLU0smNbxZvFq18b+5
YWzg1lKzeai5nO42GSLM4XS48qoACgX2LugAonpmQMBkOzMywsgHPuVkmh4hX78B
Nmn1qNwTGWInXz+UM6dv0PGWaAVScEpneWfHO6HuFKzlZJYR9bsuKUAZuAfqduaZ
whRxk5AOIRjoCjd5M8YZtacwT0sSAA6H6kCs0fxyBqwRYRJkgyKSbMm7dXhGVOPZ
Q1MBQfyJKGeKsh/Xx+OVHDi8dMdqvb01C05GrY4JPXGq9o6KtFKkv/uKPVnVA+3d
0AK9SO7PWPRto04IPEF2r4Z27Lm5Uux+jNTVlmAMHVM368WUddAso5/AjYFO8VeD
Bvo+S5ArRAHp3h8ogMHFFweJVWG2Db05uulU/QJ/vEmhaDKp1/ZFqEc14HD0alKA
jNqLPeO17GRGSm7WnUOaDcJmcZtwZiV/G4Y7iPR7AfYWd0LvDbwe7N0/7gw5zJwy
vYo7cNGulqxyl9kzlwDBzpqGD3kCtOE2Up4uXkjqrKRGBmqlwSWEs59syfN6ikol
iQtfyvTr1QreN94PACHI
=rsuM
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to