Package: zeroc-ice
Version: 3.2.1-3
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 zeroc-ice_3.2.1-3 on em64t by sbuild/amd64 0.53
...
> making all in IceUtil
> make[3]: Entering directory `/build/tbm/zeroc-ice-3.2.1/src/IceUtil'
> c++ -c -I../../include  -DICE_UTIL_API_EXPORTS -I.. -m64 -ftemplate-depth-128 
> -Wall -D_REENTRANT -DHAVE_ENDIAN_H -DHAVE_LIMITS_H -fPIC -g  ArgVector.cpp
> ArgVector.cpp: In member function 'void IceUtil::ArgVector::copyVec(int, int, 
> char**)':
> ArgVector.cpp:74: error: 'strlen' was not declared in this scope
> ArgVector.cpp:91: error: 'strcpy' was not declared in this scope
> ArgVector.cpp: In member function 'void IceUtil::ArgVector::copyVec(const 
> std::vector<std::basic_string<char, std::char_traits<char>, 
> std::allocator<char> >, std::allocator<std::basic_string<char, 
> std::char_traits<char>, std::allocator<char> > > >&)':
> ArgVector.cpp:126: error: 'strcpy' was not declared in this scope
> make[3]: *** [ArgVector.o] Error 1
> make[3]: Leaving directory `/build/tbm/zeroc-ice-3.2.1/src/IceUtil'
> make[2]: *** [all] 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