Your message dated Wed, 23 Dec 2009 16:48:07 +0000
with message-id <[email protected]>
and subject line Bug#504864: fixed in omnievents 1:2.6.2-1.2
has caused the Debian Bug report #504864,
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 [email protected]
immediately.)


-- 
504864: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504864
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: omnievents
Version: 1:2.6.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 omnievents_1:2.6.2-1 on em64t by sbuild/amd64 0.53
...
> make[2]: Entering directory `/build/tbm/omnievents-2.6.2/tools'
> g++ -c  -I../idl -I../src -pthread -I/usr/include  -DHAVE_CONFIG_H  
> -DENABLE_CLIENT_IR_SUPPORT=1 -DOMNIEVENTS_REAL_TIME_PUSH=1 -g -O2 -g -Wall 
> -O2 -g -O2 -g -Wall -O2 -fPIC  eventc.cc
> eventc.cc: In function 'int main(int, char**)':
> eventc.cc:211: error: 'EOF' was not declared in this scope
> make[2]: *** [eventc.o] Error 1
> make[2]: Leaving directory `/build/tbm/omnievents-2.6.2/tools'
> make[1]: *** [all] Error 2

--- examples/pullcons.cc~       2008-11-07 17:49:25.000000000 +0000
+++ examples/pullcons.cc        2008-11-07 17:47:47.000000000 +0000
@@ -148,6 +148,8 @@
 #  include <signal.h>
 #endif
 
+#include <cstdio>
+
 #include "CosEventComm.hh"
 #include "CosEventChannelAdmin.hh"
 #include "naming.h"
--- examples/pullsupp.cc~       2008-11-07 17:48:00.000000000 +0000
+++ examples/pullsupp.cc        2008-11-07 17:48:09.000000000 +0000
@@ -144,6 +144,8 @@
 #  include <signal.h>
 #endif
 
+#include <cstdio>
+
 #include "CosEventComm.hh"
 #include "CosEventChannelAdmin.hh"
 #include "naming.h"
--- examples/pushcons.cc~       2008-11-07 17:48:22.000000000 +0000
+++ examples/pushcons.cc        2008-11-07 17:48:30.000000000 +0000
@@ -159,6 +159,8 @@
 #  include <signal.h>
 #endif
 
+#include <cstdio>
+
 #include "CosEventComm.hh"
 #include "CosEventChannelAdmin.hh"
 #include "naming.h"
--- examples/pushsupp.cc~       2008-11-07 17:48:48.000000000 +0000
+++ examples/pushsupp.cc        2008-11-07 17:48:56.000000000 +0000
@@ -152,6 +152,8 @@
 #  include <signal.h>
 #endif
 
+#include <cstdio>
+
 #include "CosEventComm.hh"
 #include "CosEventChannelAdmin.hh"
 #include "naming.h"
--- tools/eventc.cc~    2008-11-07 17:45:46.000000000 +0000
+++ tools/eventc.cc     2008-11-07 17:46:09.000000000 +0000
@@ -184,6 +184,8 @@
 #  include <signal.h>
 #endif
 
+#include <cstdio>
+
 #include "omniEvents.hh"
 #include "naming.h"
 
--- tools/eventf.cc~    2008-11-07 17:46:30.000000000 +0000
+++ tools/eventf.cc     2008-11-07 17:46:39.000000000 +0000
@@ -46,6 +46,8 @@
 #  include <iostream.h>
 #endif
 
+#include <cstdio>
+
 #ifdef HAVE_STD_IOSTREAM
 using namespace std;
 #endif
--- tools/rmeventc.cc~  2008-11-07 17:46:58.000000000 +0000
+++ tools/rmeventc.cc   2008-11-07 17:47:05.000000000 +0000
@@ -46,6 +46,8 @@
 #  include <iostream.h>
 #endif
 
+#include <cstdio>
+
 #ifdef HAVE_STD_IOSTREAM
 using namespace std;
 #endif

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



--- End Message ---
--- Begin Message ---
Source: omnievents
Source-Version: 1:2.6.2-1.2

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

libomnievents-dbg_2.6.2-1.2_i386.deb
  to main/o/omnievents/libomnievents-dbg_2.6.2-1.2_i386.deb
libomnievents-dev_2.6.2-1.2_i386.deb
  to main/o/omnievents/libomnievents-dev_2.6.2-1.2_i386.deb
libomnievents2_2.6.2-1.2_i386.deb
  to main/o/omnievents/libomnievents2_2.6.2-1.2_i386.deb
omnievents-doc_2.6.2-1.2_all.deb
  to main/o/omnievents/omnievents-doc_2.6.2-1.2_all.deb
omnievents_2.6.2-1.2.diff.gz
  to main/o/omnievents/omnievents_2.6.2-1.2.diff.gz
omnievents_2.6.2-1.2.dsc
  to main/o/omnievents/omnievents_2.6.2-1.2.dsc
omnievents_2.6.2-1.2_i386.deb
  to main/o/omnievents/omnievents_2.6.2-1.2_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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Paleino <[email protected]> (supplier of updated omnievents 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 [email protected])


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

Format: 1.8
Date: Mon, 21 Dec 2009 17:05:30 +0100
Source: omnievents
Binary: omnievents libomnievents2 libomnievents-dev omnievents-doc 
libomnievents-dbg
Architecture: source all i386
Version: 1:2.6.2-1.2
Distribution: unstable
Urgency: low
Maintainer: Debian CORBA Team <[email protected]>
Changed-By: David Paleino <[email protected]>
Description: 
 libomnievents-dbg - omniORB event service debugging symbols
 libomnievents-dev - omniORB event service development files
 libomnievents2 - omniORB event service shared library
 omnievents - omniORB event service
 omnievents-doc - omniORB event service documentation
Closes: 504864
Changes: 
 omnievents (1:2.6.2-1.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix FTBFS with GCC 4.4, added missing #includes, thanks to Martin
     Michlmayr (Closes: #504864)
Checksums-Sha1: 
 81decb692d3ee3b2cc7df55a3ba80a2be2b3ae10 1474 omnievents_2.6.2-1.2.dsc
 ad10083546b40bd34c8bc3dd191069b582cb4837 4678 omnievents_2.6.2-1.2.diff.gz
 f73b53a722fd7197b3770cb90856f14f44eb3932 3910620 
omnievents-doc_2.6.2-1.2_all.deb
 98ffc6b62717b962f32b0ec4da2573c9c769d0b4 294554 omnievents_2.6.2-1.2_i386.deb
 77198a6a3ace45758459090ac0b33f7ddc219005 278074 
libomnievents2_2.6.2-1.2_i386.deb
 2dfcf77079d3e64f326e4062b218f2ce81c997a4 332364 
libomnievents-dev_2.6.2-1.2_i386.deb
 9c5ff23528f9900fc00e865e94679efcae542cb3 2093276 
libomnievents-dbg_2.6.2-1.2_i386.deb
Checksums-Sha256: 
 d881d20ad5f078776f26eb887ba0a7b387e59ceec317da89f35676321c938c1c 1474 
omnievents_2.6.2-1.2.dsc
 7feeff581b8a33b9a35848d9fcf0ca9e8b46ec4cd1cb24a7b68cd2f3fa809c10 4678 
omnievents_2.6.2-1.2.diff.gz
 ecb543ca0b3af276b3b8b08e792e90bcb0288910e4480275985265b9ec835e32 3910620 
omnievents-doc_2.6.2-1.2_all.deb
 74125d1c3928ff20d0afe34833d99b9e081c523c38fcd6de9dd758ea79032e7f 294554 
omnievents_2.6.2-1.2_i386.deb
 6df34dd0b2b69a972051bfab1d21f4e7010606b3a7517d7e4dc4ac226c082fda 278074 
libomnievents2_2.6.2-1.2_i386.deb
 f3b119b911707189924c629e4c546b5d68b90c28998d43b2daf140106f7f2d62 332364 
libomnievents-dev_2.6.2-1.2_i386.deb
 efad8b8b6497717e87d5ac14ec9708247aca4e136bec4c2bc72e731c20933daa 2093276 
libomnievents-dbg_2.6.2-1.2_i386.deb
Files: 
 94021bd3e8d1c3a64286691f50313b8b 1474 net optional omnievents_2.6.2-1.2.dsc
 adb92ac3f63763854fd45d5ca64607c8 4678 net optional omnievents_2.6.2-1.2.diff.gz
 01a738a5056615757cda4653d144305d 3910620 doc optional 
omnievents-doc_2.6.2-1.2_all.deb
 9efe071a3706e22ab96b4f8ae0575e0c 294554 net optional 
omnievents_2.6.2-1.2_i386.deb
 54097896c6337b549e726c2a05511b6a 278074 libs optional 
libomnievents2_2.6.2-1.2_i386.deb
 da5a7dc1d5650fa04ff53cf9e4bc6720 332364 libdevel optional 
libomnievents-dev_2.6.2-1.2_i386.deb
 9bf47bb6ae7ed0f0725f2a25a5890a1e 2093276 debug extra 
libomnievents-dbg_2.6.2-1.2_i386.deb

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

iEYEARECAAYFAksvn7MACgkQ5qqQFxOSsXQKiwCgnrqNjqUtNnUDrG/QSlb7Bq3S
q1QAn2nqaVgjxochjqzw/+RquDReO5Ay
=9JnM
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to