Package: libcapsinetwork
Version: 0.3.0-2
Usertags: ftbfs-gcc-4.3
Tags: patch

Your package fails to build with GCC 4.3.  Version 4.3 has not been
released yet but I'm building with a snapshot in order to find errors
and give people an advance warning.  In GCC 4.3, the C++ header
dependencies have been cleaned up.  The advantage of this is that
programs will compile faster.  The downside is that you actually
need to directly #include everything you use (but you really should
do this anyway, otherwise your program won't work with any compiler
other than GCC).  Some background of this can be found at
http://gcc.gnu.org/PR28080

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

> Automatic build of libcapsinetwork_0.3.0-2 on coconut0 by sbuild/ia64 0.49
...
>  g++ -DHAVE_CONFIG_H -I. -I. -I.. -g -Wall -O2 -c listener.cpp  -fPIC -DPIC 
> -o .libs/listener.o
> In file included from listener.cpp:36:
> listenport.h:38: warning: type qualifiers ignored on function return type
> listenport.h:39: warning: type qualifiers ignored on function return type
> In file included from listener.cpp:37:
> socket.h:45: warning: type qualifiers ignored on function return type
> listener.cpp: In member function 'void Listener::checkActivity()':
> listener.cpp:103: error: 'exit' was not declared in this scope

--- src/listener.cpp~   2007-04-02 10:38:46.000000000 +0000
+++ src/listener.cpp    2007-04-02 10:38:56.000000000 +0000
@@ -31,6 +31,7 @@
 
 #include <netdb.h>
 #include <unistd.h>
+#include <cstdlib>
 
 #include "listener.h"
 #include "listenport.h"
--- src/server.cpp~     2007-04-02 10:39:16.000000000 +0000
+++ src/server.cpp      2007-04-02 10:39:25.000000000 +0000
@@ -25,6 +25,7 @@
 // Example server demonstrating libcapsi_network.
 
 #include <string>
+#include <cstdlib>
 #include <stdio.h>
 
 // In real applications, use the following include instead of the local.

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