Re: [Cppunit-devel] Question about CppUnit on Solaris8
Brought to you by:
blep
From: Baptiste L. <gai...@fr...> - 2002-08-27 20:52:09
|
Would you mind trying with cppunit 1.9.8 ? You can get it there: http://cppunit.sourceforge.net/snapshot/ I remember changing the main() implementation, but not the specific. = Also, the TestFactoryRegistry is more robust concerning TestFactory = initialization/uninitialization. Baptiste. ----- Original Message -----=20 From: wangleiyu=20 To: cpp...@li...=20 Sent: Monday, August 26, 2002 11:40 AM Subject: [Cppunit-devel] Question about CppUnit on Solaris8 hello, these times i'm using CppUnit(Release 1.8.0) to do unit = testing. On win2000 & linux, it's ok(and easy to use :) ), but on solaris8 it = core dumped. what i did is as following: 1. gunzip cppunit-1.8.0.tar.gz 2. tar xvf cppunit-1.8.0.tar 3. cd cppunit-1.8.0 4. configure ( no option, no argument)=20 (there was a warning, and the result is as following) 5. make (ok) 6. make check=20 the program throwed an exception and then core dumped : make check-TESTS make[3]: Entering directory `/export/home/Tools/CppUnit/cppunit- = 1.8.0/examples/hierarchy' ..The following test fails, this is intended: Abort - core dumped FAIL: hierarchy =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 1 of 1 tests failed =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 my machine environment: solaris8 gcc2.95.3 Hope your help and lots of thanks :) = Yours sincerely=20 = wangleiyu 2002-08-26 Configuration Result: checking for a BSD compatible install... config/install-sh -c checking whether build environment is sane... yes checking for mawk... no checking for gawk... gawk checking whether make sets ${MAKE}... yes checking whether make sets ${MAKE}... (cached) yes checking for a BSD compatible install... config/install-sh -c checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for executable suffix... checking for object suffix... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for style of include used by make... GNU checking dependency style of gcc... gcc checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc checking build system type... sparc-sun-solaris2.8 checking host system type... sparc-sun-solaris2.8 checking for ld used by GCC... /usr/ccs/bin/ld checking if the linker (/usr/ccs/bin/ld) is GNU ld... no checking for /usr/ccs/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/ccs/bin/nm -p checking whether ln -s works... yes checking how to recognise dependant libraries... pass_all checking command to parse /usr/ccs/bin/nm -p output... ok checking how to run the C++ preprocessor... g++ -E checking for dlfcn.h... yes checking for ranlib... ranlib checking for strip... strip checking for objdir... .libs checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... no checking if we can lock with hard links... yes checking if gcc supports -fno-rtti -fno-exceptions... yes checking whether the linker (/usr/ccs/bin/ld) supports shared = libraries... *** Warning: Releases of GCC earlier than version 3.0 cannot reliably *** create self contained shared libraries on Solaris systems, without *** introducing a dependency on libgcc.a. Therefore, libtool is = disabling *** -no-undefined support, which will at least allow you to build = shared *** libraries. However, you may find that when you link such = libraries *** into an application without using GCC, you have to manually add *** `gcc --print-libgcc-file-name` to the link command. We urge you = to *** upgrade to a newer version of GCC. Another option is to rebuild = your *** current GCC to use the GNU linker from GNU binutils 2.9.1 or = newer. yes checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... no checking dynamic linker characteristics... solaris2.8 ld.so checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes creating libtool checking for doxygen... no checking for cmath... yes checking whether the compiler supports Run-Time Type Identification... = yes checking whether the compiler implements namespaces... yes checking whether std::string::compare takes a string in argument 1... = yes checking whether the compiler has stringstream... yes checking whether the library defines class strstream... checking for = strstream ... yes yes configure: creating ./config.status config.status: creating Makefile config.status: creating cppunit.spec config.status: creating cppunit-config config.status: creating src/Makefile config.status: creating src/cppunit/Makefile config.status: creating include/Makefile config.status: creating include/cppunit/Makefile config.status: creating include/cppunit/extensions/Makefile config.status: creating include/cppunit/ui/Makefile config.status: creating include/cppunit/ui/mfc/Makefile config.status: creating include/cppunit/ui/qt/Makefile config.status: creating include/cppunit/ui/text/Makefile config.status: creating doc/Makefile config.status: creating doc/Doxyfile config.status: creating examples/Makefile config.status: creating examples/hierarchy/Makefile config.status: creating examples/cppunittest/Makefile config.status: creating config/config.h config.status: config/config.h is unchanged creating include/cppunit/config-auto.h - prefix CPPUNIT for = config/config.h de fines |