Package: skstream
Version: 0.3.6-2
Usertags: ftbfs-gcc-4.3

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).  There's some more information about this at
http://www.cyrius.com/journal/2007/05/10#gcc-4.3-include

You can reproduce this problem with gcc-snapshot from unstable.  Note
that Red Hat, Novell and Ubuntu have done some work getting packages
to build with GCC 4.3 so there might be patches floating around
somewhere.  I suggest you talk to your upstream.

> Automatic build of skstream_0.3.6-2 on em64t by sbuild/amd64 0.53
...
>  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I.. -I.. -g -O2 -Wall -DNDEBUG 
> -c skstream.cpp  -fPIC -DPIC -o .libs/skstream.o
> skstream.cpp: In constructor 'socketbuf::socketbuf(SOCKET_TYPE, unsigned int, 
> unsigned int)':
> skstream.cpp:154: error: '::memset' has not been declared
> skstream.cpp: In member function 'bool dgram_socketbuf::setTarget(const 
> std::string&, unsigned int, int)':
> skstream.cpp:393: error: '::memcpy' has not been declared
> skstream.cpp: In member function 'void tcp_socket_stream::open(const 
> std::string&, int, bool)':
> skstream.cpp:740: error: '::memcpy' has not been declared
> skstream.cpp: In member function 'bool tcp_socket_stream::isReady(unsigned 
> int)':
> skstream.cpp:1008: error: '::memcpy' has not been declared
> skstream.cpp: In member function 'int 
> dgram_socket_stream::bindToIpService(int, int, int)':
> skstream.cpp:1110: error: '::memcpy' has not been declared
> make[3]: *** [skstream.lo] Error 1

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