Package: muparser Version: 1.28-1 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 muparser_1.28-1 on em64t by sbuild/amd64 0.53 ... > x86_64-linux-gnu-g++ -c -o muParser_dll_muParserTest.o -DNDEBUG > -DMUPARSER_DLL -DMUPARSERLIB_EXPORTS -I./include -fPIC -DPIC -O2 > ./src/muParserTest.cpp > In file included from ./src/muParserTest.cpp:26: > ./include/muParserTest.h: In static member function 'static mu::value_type > mu::Test::ParserTester::Rnd(mu::value_type)': > ./include/muParserTest.h:90: error: 'rand' is not a member of 'std' > ./include/muParserTest.h:90: error: 'RAND_MAX' was not declared in this scope > ./include/muParserTest.h: In static member function 'static mu::value_type > mu::Test::ParserTester::RndWithString(const mu::char_type*)': > ./include/muParserTest.h:95: error: 'rand' is not a member of 'std' > ./include/muParserTest.h:95: error: 'RAND_MAX' was not declared in this scope > ./src/muParserTest.cpp: In member function 'void > mu::Test::ParserTester::Abort() const': > ./src/muParserTest.cpp:1148: error: 'exit' was not declared in this scope > make[1]: *** [muParser_dll_muParserTest.o] Error 1 -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
