Package: rig Version: 1.10-4 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 rig_1.10-4 on em64t by sbuild/amd64 0.53 ... > g++ -O2 -g rig.cc -o rig -Wall -DDATADIR="\"/usr/share/rig\"" > rig.cc: In function 'T getrandnum(T)': > rig.cc:65: error: there are no arguments to 'memcpy' that depend on a > template parameter, so a declaration of 'memcpy' must be available > rig.cc:65: error: (if you use '-fpermissive', G++ will accept your code, but > allowing the use of an undeclared name is deprecated) > rig.cc: In function 'T getrandnum(T) [with T = unsigned int]': > rig.cc:302: instantiated from here > rig.cc:65: error: 'memcpy' was not declared in this scope > rig.cc: In function 'T getrandnum(T) [with T = long unsigned int]': > rig.cc:79: instantiated from 'typename T::value_type getrandpart(T&) [with > T = 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> > > >]' > rig.cc:301: instantiated from here > rig.cc:65: error: 'memcpy' was not declared in this scope > make[1]: *** [rig] Error 1 -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
