[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#504862: marked as done (FTBFS with GCC 4.4: missing #include)

Your message dated Mon, 10 Nov 2008 19:17:04 +0000
with message-id <E1KzcG0-0006a9-2G@ries.debian.org>
and subject line Bug#504862: fixed in anymeal 0.30-8
has caused the Debian Bug report #504862,
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 owner@bugs.debian.org
immediately.)


-- 
504862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504862
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: anymeal
Version: 0.30-7
User: debian-gcc@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 anymeal_0.30-7 on em64t by sbuild/amd64 0.53
...
> g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/xercesc -I/usr/include/xalan -I/usr/include/xalanc -I/usr/include/kde -I/usr/share/qt3/include -I.   -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -O2 -g -O2 -g -Wall -O2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -fexceptions -I/usr/include/xalanc -I/usr/include/xalan  -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -O2 -g -O2 -g -Wall -O2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -fexceptions  -c -o mysqlDaemon.o `test -f 'mysqlDaemon.cpp' || echo './'`mysqlDaemon.cpp
> mysqlDaemon.cpp: In static member function 'static std::string MySQLDaemon::create(const std::string&, const std::string&)':
> mysqlDaemon.cpp:94: error: 'popen' was not declared in this scope
> mysqlDaemon.cpp:98: error: 'feof' was not declared in this scope
> mysqlDaemon.cpp:101: error: no matching function for call to 'getline(char**, size_t*, FILE*&)'
> make[3]: *** [mysqlDaemon.o] Error 1
> make[3]: Leaving directory `/build/tbm/anymeal-0.30/src'

--- src/mysqlDaemon.cpp~	2008-11-07 17:37:07.000000000 +0000
+++ src/mysqlDaemon.cpp	2008-11-07 17:37:13.000000000 +0000
@@ -15,6 +15,7 @@
    with AnyMeal; if not, contact one of the authors of this software. */
 #include <boost/shared_array.hpp>
 #include <cstddef>
+#include <cstdio>
 #include <cstdlib>
 #include <errno.h>
 #include <fcntl.h>

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

--- End Message ---
--- Begin Message --- 
Source: anymeal
Source-Version: 0.30-8

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

anymeal_0.30-8.diff.gz
  to pool/main/a/anymeal/anymeal_0.30-8.diff.gz
anymeal_0.30-8.dsc
  to pool/main/a/anymeal/anymeal_0.30-8.dsc
anymeal_0.30-8_i386.deb
  to pool/main/a/anymeal/anymeal_0.30-8_i386.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 504862@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi <morph@debian.org> (supplier of updated anymeal 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 ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Mon, 10 Nov 2008 19:51:32 +0100
Source: anymeal
Binary: anymeal
Architecture: source i386
Version: 0.30-8
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Sandro Tosi <morph@debian.org>
Description: 
 anymeal    - cookbook database for storing recipes
Closes: 504862
Changes: 
 anymeal (0.30-8) unstable; urgency=low
 .
   * QA upload.
   * debian/control
     - set maint to QA Group
     - removed previous maint and uploaders (in agreement with Tony)
     - bump Standards-Version to 3.8.0
       + added debian/README.source
     - removed article from short description
     - removed XS-DM-Upload-Allowed field
   * debian/patches/50_bts-504862_ftbfs_gcc4.4.dpatch
     - added to fix a FTBFS if compiled with GCC 4.4; thanks to Martin Michlmayr
       for the report and the patch; Closes: #504862
Checksums-Sha1: 
 7ba03b76407204014ae9f92828ecf95addfafbd2 1220 anymeal_0.30-8.dsc
 42c3b38f7649f3c93908488797a5c053e9734e85 454223 anymeal_0.30-8.diff.gz
 08e4ab46e663b14ff7fa59bcbbcff709d26ac753 479398 anymeal_0.30-8_i386.deb
Checksums-Sha256: 
 63a121c3b185811d884a7a1203b272193e73bed8e8390d4631ef56636471ddc7 1220 anymeal_0.30-8.dsc
 c66ba275d3b20d44a9529b662dab3b52011f1bc8115a539454a36aa71e730159 454223 anymeal_0.30-8.diff.gz
 2aa4085f3246e04ad76e37cda81cf9ec14db4e735ef71d14c4afbfd5b06d6a3c 479398 anymeal_0.30-8_i386.deb
Files: 
 cd10f24c0f2e4d82f61208b81a73eff2 1220 kde optional anymeal_0.30-8.dsc
 64b3a56cbc5b100ca06d2cfe4642a291 454223 kde optional anymeal_0.30-8.diff.gz
 b69754a017712deae1cf286b50b47b8c 479398 kde optional anymeal_0.30-8_i386.deb

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

iEYEARECAAYFAkkYhzMACgkQAukwV0RN2VDitwCaAqUzj1+nMElBHs5u4Uzh5XFv
WLYAnj1xKqSrgJIeWwC7ayWMJ7QV45wh
=8NuO
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: