Thread: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem
Brought to you by:
blep
From: Stanley S. <su...@t-...> - 2002-04-22 15:36:20
|
I'm still having some problmes on Solaris 8, using the Forte 6 compiler. = I removed all my local files and got a fresh CVS snapshot. Here's = there first error: cd . && autoconf autoconf: warning: both `configure.ac' and `configure.in' are present. autoconf: warning: proceeding with `configure.ac'. configure.ac:37: error: do not use LIBOBJS directly, use AC_LIBOBJ (see = section `AC_LIBOBJ vs. LIBOBJS' I'm using GNU make, by the way, as well as the GNU versions of most of = the utilities. -----Original Message----- From: Baptiste Lepilleur [mailto:gai...@fr...] Sent: Sun 21-Apr-02 08:28 To: cpp...@li... Cc:=09 Subject: [Cppunit-devel] CppUnit 1.9.6 tar ball New snapshot. The problem on Unix should be fixed. Thanks to all = those who helped ! KNOWN PROBLEMS: - TestPlugIn project has not been removed from the Examples workspace = (just click cancel) - Money example is missing dependency with cppunit.dsp As usal, the snapshop can be found at: http://cppunit.sourceforge.net/snapshot/ http://cppunit.sourceforge.net/snapshot/cppunit-1.9.6.tar.gz http://cppunit.sourceforge.net/snapshot/cppunit-docs-1.9.6.tar.gz New in CppUnit 1.9.6: ---------------------- - DllPlugInTester can be parametrized from command line - Two test listener plug-in examples - An 'hello world' example & getting started document : Money - Contribution: generic makefile for Borland 5.5 free compiler. - Bug fixes * DllPlugInTester: - Advanced command line to support miscellaneous listener outputer. Parameters can now be passed to test plug-in: -c --compiler Use CompilerOutputter -x --xml [filename] Use XmlOutputter (if filename is omitted, then output to cout or cerr. -s --xsl stylesheet XML style sheet for XML Outputter -e --encoding encoding XML file encoding (UTF8, shift_jis, ISO-8859-1...) -b --brief-progress Use BriefTestProgressListener (default is TextTestProgressListener) -n --no-progress Show no test progress (disable default TextTestProgressListener) -t --text Use TextOutputter -o --cout Ouputters output to cout instead of the default cerr. filename[=3D"options"] Many filenames can be specified. They are the name of the test plug-ins to load. Optional plug-ins parameters can be specified after the filename by adding '=3D'. [:testpath] Optional. Only one test path can be specified. It must be prefixed with ':'. See TestPath constructor for syntax. 'parameters' (test plug-in or XML filename, test path...) may contains spaces if double quoted. Quote may be escaped with \". Some examples of command lines: DllPlugInTesterd_dll.exe -b -x tests.xml -c simple_plugind.dll CppUnitTestPlugInd.dll Will load 2 tests plug-ins (available in lib/), use the brief test progress, output the result in XML in file tests.xml and also output the result using the compiler outputter. DllPlugInTesterd_dll.exe ClockerPlugInd.dll=3D"flat" -n = CppUnitTestPlugInd.dll Will load the 2 test plug-ins, and pass the parameter string "flat" to the Clocker plug-in, disable test progress. Clocker being a test listener plug-ins (it doesn't implements any tests, it just register a TestListener), this is equivalent to say 'run all the test of CppUnitTestPlugIn and use ClockerPlugIn as a TestLisener'. DllPlugInTesterd_dll.exe CppUnitTestPlugInd.dll :Core Will run the test named "Core" (a suite in the present case ) of the test plug-in. * Documentation - New getting started documentation. Not completed yet, but probably a good complement to the current cookbook. Explore the creation of the Money example. * Examples - Money (examples/Money): the 'hello world' example. Unit tests for a simple Money class. - DllPlugInTesterTest (src/DllPlugInTester/DllPlugInTester.dsp): unit tests for CommandLineParser. Not really an example, but only slightly more complex than Money. - ClockerPlugIn (examples/ClockerPlugIn): a test listener plug-in that track tests and test suites running time. Parameter: "flat" for a reporting with a flattened tree. - DumperPlugIn (examples/DumperPlugIn): a test listener plug-in that dump the test tree as it run. Paramater: "flat" for a reporting with a flattened tree. - CppUnitTestPlugIn (examples/cppunitest/CppUnitTestPlugIn.dsp): CppUnit's test suite as a test plug-in. * Contribution - Contributed by project cuppa team (http://sourceforge.jp/projects/cuppa/): - Makefile for CppUnit with Borland C++ 5.5 free compiler: does not depend on a specific CppUnit version. * Compatiblity breaks - DllPlugInTester: (1.9.4 only), should add -c to DllPlugInTester command line. * Bug Fix: - DynamicLibaryManager did not report the library name when loading a a library. - BeosDynamicLibraryManager: fixed thanks to Shibu Yoshiki ('cuppa' project team). - Broken build on Unix should be fixed for most (thanks to Jeffrey Morgan). Enjoy, Baptiste. --- Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/ _______________________________________________ Cppunit-devel mailing list Cpp...@li... https://lists.sourceforge.net/lists/listinfo/cppunit-devel |
From: Stanley S. <su...@t-...> - 2002-04-22 17:15:27
|
Hmm, let me delete EVERYTHING and start over from loggin in. I'm not = sure why, but I've had some very strange behaviors from CVS before, like = recursive directories with GAIM. We use CVS everyday for our own = projects, and we're spread out over 3 continents without any problems, = but we use it a little differently (such as locking a module, and = "moving" it's access tokens to a local server before doing commits). -----Original Message----- From: Steve M. Robbins [mailto:ste...@vi...] Sent: Mon 22-Apr-02 11:06 To: Stanley Sutton Cc: CppUnit Development Subject: Re: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem On Mon, Apr 22, 2002 at 10:36:59AM -0500, Stanley Sutton wrote: >=20 > I'm still having some problmes on Solaris 8, using the Forte 6 = compiler. I > removed all my local files and got a fresh CVS snapshot. Here's there = first > error: >=20 > cd . && autoconf > autoconf: warning: both `configure.ac' and `configure.in' are present. > autoconf: warning: proceeding with `configure.ac'. ??? How did that happen? I just ran "cvs update" and there is only configure.in here. > configure.ac:37: error: do not use LIBOBJS directly, use AC_LIBOBJ > (see section `AC_LIBOBJ vs. LIBOBJS' Neither is there any "LIBOBJ" in my configure.in. =20 Something is fishy. -S --=20 by Rocket to the Moon, by Airplane to the Rocket, by Taxi to the Airport, by Frontdoor to the Taxi, by throwing back the blanket and laying down the legs ... - They Might Be Giants |
From: Stanley S. <su...@t-...> - 2002-04-22 19:36:53
|
Here's the latest problem: gmake[2]: Entering directory = `/space/local_users/sutton/projects/cppunit/src/DllPlugInTester' /bin/bash ../../libtool --mode=3Dlink CC -g -o DllPlugInTester -ldl = DllPlugInTester.o CommandLineParser.o ../../src/cppunit/libcppunit.la=20 CC -g -o .libs/DllPlugInTester DllPlugInTester.o CommandLineParser.o = -ldl ../../src/cppunit/.libs/libcppunit.so -R/home/sutton/solaris/lib ild: (undefined symbol) unsigned = std::deque<CppUnit::TestFailure*,std::allocator<CppUnit::TestFailure*> = >::__buffer_size() -- referenced in = ../../src/cppunit/.libs/libcppunit.so ild: (undefined symbol) = std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*> >::iterator = std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*> = >::erase(std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*> = >::iterator,std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*> = >::iterator) -- referenced in ../../src/cppunit/.libs/libcppunit.so (plus many, many more in the same vein) As near as I can figure, the problem is in the template instantation. I = know we've had problems with that in our code before, do to a compiler = inker bug. We use the linker option "-z now" on all of our Solaris = compiles, as well as absolute disk paths rather than relative ones to = keep from confusing the compiler/linker. However, I haven't been able = to figure out how to add the "-z now" to the linker. ".configure = --prefix-/space/local_users/sutton/solaris LD_FLAGS=3D'-z now'" didn't = seem to have any affect. -----Original Message----- From: Baptiste Lepilleur [mailto:gai...@fr...] Sent: Mon 22-Apr-02 11:24 To: Stanley Sutton; cpp...@li... Cc:=09 Subject: Re: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem Did you follow the step indicated in Readme.CVS (and if those don't = work, did you try the lastest tar ball ?): * Unix: To generate the configure script, you need several auxiliary tools. The version numbers are minimal: later versions should also work. autoconf 2.50 - see http://www.gnu.org/directory/autoconf.html automake 1.4 - see http://www.gnu.org/directory/automake.html libtool 1.4 - see http://www.gnu.org/directory/libtool.html After checking the sources out from CVS, you need to run the script sh autogen.sh from the top-level source directory (i.e. the one containing this file). This needs only to be done once. Baptiste. ----- Original Message ----- From: "Stanley Sutton" <su...@t-...> To: "Baptiste Lepilleur" <gai...@fr...>; <cpp...@li...> Sent: Monday, April 22, 2002 5:36 PM Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem I'm still having some problmes on Solaris 8, using the Forte 6 compiler. = I removed all my local files and got a fresh CVS snapshot. Here's there = first error: cd . && autoconf autoconf: warning: both `configure.ac' and `configure.in' are present. autoconf: warning: proceeding with `configure.ac'. configure.ac:37: error: do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ vs. LIBOBJS' I'm using GNU make, by the way, as well as the GNU versions of most of = the utilities. -----Original Message----- From: Baptiste Lepilleur [mailto:gai...@fr...] Sent: Sun 21-Apr-02 08:28 To: cpp...@li... Cc: Subject: [Cppunit-devel] CppUnit 1.9.6 tar ball New snapshot. The problem on Unix should be fixed. Thanks to all = those who helped ! KNOWN PROBLEMS: - TestPlugIn project has not been removed from the Examples workspace = (just click cancel) - Money example is missing dependency with cppunit.dsp As usal, the snapshop can be found at: http://cppunit.sourceforge.net/snapshot/ http://cppunit.sourceforge.net/snapshot/cppunit-1.9.6.tar.gz http://cppunit.sourceforge.net/snapshot/cppunit-docs-1.9.6.tar.gz New in CppUnit 1.9.6: ---------------------- - DllPlugInTester can be parametrized from command line - Two test listener plug-in examples - An 'hello world' example & getting started document : Money - Contribution: generic makefile for Borland 5.5 free compiler. - Bug fixes * DllPlugInTester: - Advanced command line to support miscellaneous listener outputer. Parameters can now be passed to test plug-in: -c --compiler Use CompilerOutputter -x --xml [filename] Use XmlOutputter (if filename is omitted, then output to cout or cerr. -s --xsl stylesheet XML style sheet for XML Outputter -e --encoding encoding XML file encoding (UTF8, shift_jis, ISO-8859-1...) -b --brief-progress Use BriefTestProgressListener (default is TextTestProgressListener) -n --no-progress Show no test progress (disable default TextTestProgressListener) -t --text Use TextOutputter -o --cout Ouputters output to cout instead of the default cerr. filename[=3D"options"] Many filenames can be specified. They are the name of the test plug-ins to load. Optional plug-ins parameters can be specified after the filename by adding '=3D'. [:testpath] Optional. Only one test path can be specified. It must be prefixed with ':'. See TestPath constructor for syntax. 'parameters' (test plug-in or XML filename, test path...) may contains spaces if double quoted. Quote may be escaped with \". Some examples of command lines: DllPlugInTesterd_dll.exe -b -x tests.xml -c simple_plugind.dll CppUnitTestPlugInd.dll Will load 2 tests plug-ins (available in lib/), use the brief test progress, output the result in XML in file tests.xml and also output the result using the compiler outputter. DllPlugInTesterd_dll.exe ClockerPlugInd.dll=3D"flat" -n = CppUnitTestPlugInd.dll Will load the 2 test plug-ins, and pass the parameter string "flat" to the Clocker plug-in, disable test progress. Clocker being a test listener plug-ins (it doesn't implements any tests, it just register a TestListener), this is equivalent to say 'run all the test of CppUnitTestPlugIn and use ClockerPlugIn as a TestLisener'. DllPlugInTesterd_dll.exe CppUnitTestPlugInd.dll :Core Will run the test named "Core" (a suite in the present case ) of the test plug-in. * Documentation - New getting started documentation. Not completed yet, but probably a good complement to the current cookbook. Explore the creation of the Money example. * Examples - Money (examples/Money): the 'hello world' example. Unit tests for a simple Money class. - DllPlugInTesterTest (src/DllPlugInTester/DllPlugInTester.dsp): unit tests for CommandLineParser. Not really an example, but only slightly more complex than Money. - ClockerPlugIn (examples/ClockerPlugIn): a test listener plug-in that track tests and test suites running time. Parameter: "flat" for a reporting with a flattened tree. - DumperPlugIn (examples/DumperPlugIn): a test listener plug-in that dump the test tree as it run. Paramater: "flat" for a reporting with a flattened tree. - CppUnitTestPlugIn (examples/cppunitest/CppUnitTestPlugIn.dsp): CppUnit's test suite as a test plug-in. * Contribution - Contributed by project cuppa team (http://sourceforge.jp/projects/cuppa/): - Makefile for CppUnit with Borland C++ 5.5 free compiler: does not depend on a specific CppUnit version. * Compatiblity breaks - DllPlugInTester: (1.9.4 only), should add -c to DllPlugInTester command line. * Bug Fix: - DynamicLibaryManager did not report the library name when loading a a library. - BeosDynamicLibraryManager: fixed thanks to Shibu Yoshiki ('cuppa' project team). - Broken build on Unix should be fixed for most (thanks to Jeffrey Morgan). Enjoy, Baptiste. --- Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/ _______________________________________________ Cppunit-devel mailing list Cpp...@li... https://lists.sourceforge.net/lists/listinfo/cppunit-devel |
From: Stanley S. <su...@t-...> - 2002-04-22 17:37:44
|
Yes, I'm up to date on the tools, although since I don't have root = access on my workstation, I use the --prefix on configure. Starting = over from scratch fixed that particular problem. Once again, I'm = getting: CC -DHAVE_CONFIG_H -I. -I. -I../../config -I../../include = -I../../include -g -Wp,-MD,.deps/DynamicLibraryManager.pp -c = DynamicLibraryManager.cpp -KPIC -DPIC CC: Warning: Option -Wp,-MD,.deps/DynamicLibraryManager.pp passed to ld, = if ld is invoked, ignored otherwise "../../include/cppunit/plugin/DynamicLibraryManagerException.h", line = 28: Error: Identifier expected instead of "}". 1 Error(s) detected. This is due to the enum in the include file, which ends in a ",}", which = the Solaris compiler treats as an error. Also, the "-Wp,-MD,.deps/..." = doesn't seem to mean anything to the Solaris compiler, so the cp and the = tr both fail. If the purpose of the option is to generat dependancies, = the -xM generates a dependancy list to stdout, -xM1 generates a unique = list with the /usr/include files filtered out. -----Original Message----- From: Baptiste Lepilleur [mailto:gai...@fr...] Sent: Mon 22-Apr-02 11:24 To: Stanley Sutton; cpp...@li... Cc:=09 Subject: Re: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem Did you follow the step indicated in Readme.CVS (and if those don't = work, did you try the lastest tar ball ?): * Unix: To generate the configure script, you need several auxiliary tools. The version numbers are minimal: later versions should also work. autoconf 2.50 - see http://www.gnu.org/directory/autoconf.html automake 1.4 - see http://www.gnu.org/directory/automake.html libtool 1.4 - see http://www.gnu.org/directory/libtool.html After checking the sources out from CVS, you need to run the script sh autogen.sh from the top-level source directory (i.e. the one containing this file). This needs only to be done once. Baptiste. ----- Original Message ----- From: "Stanley Sutton" <su...@t-...> To: "Baptiste Lepilleur" <gai...@fr...>; <cpp...@li...> Sent: Monday, April 22, 2002 5:36 PM Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem I'm still having some problmes on Solaris 8, using the Forte 6 compiler. = I removed all my local files and got a fresh CVS snapshot. Here's there = first error: cd . && autoconf autoconf: warning: both `configure.ac' and `configure.in' are present. autoconf: warning: proceeding with `configure.ac'. configure.ac:37: error: do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ vs. LIBOBJS' I'm using GNU make, by the way, as well as the GNU versions of most of = the utilities. -----Original Message----- From: Baptiste Lepilleur [mailto:gai...@fr...] Sent: Sun 21-Apr-02 08:28 To: cpp...@li... Cc: Subject: [Cppunit-devel] CppUnit 1.9.6 tar ball New snapshot. The problem on Unix should be fixed. Thanks to all = those who helped ! KNOWN PROBLEMS: - TestPlugIn project has not been removed from the Examples workspace = (just click cancel) - Money example is missing dependency with cppunit.dsp As usal, the snapshop can be found at: http://cppunit.sourceforge.net/snapshot/ http://cppunit.sourceforge.net/snapshot/cppunit-1.9.6.tar.gz http://cppunit.sourceforge.net/snapshot/cppunit-docs-1.9.6.tar.gz New in CppUnit 1.9.6: ---------------------- - DllPlugInTester can be parametrized from command line - Two test listener plug-in examples - An 'hello world' example & getting started document : Money - Contribution: generic makefile for Borland 5.5 free compiler. - Bug fixes * DllPlugInTester: - Advanced command line to support miscellaneous listener outputer. Parameters can now be passed to test plug-in: -c --compiler Use CompilerOutputter -x --xml [filename] Use XmlOutputter (if filename is omitted, then output to cout or cerr. -s --xsl stylesheet XML style sheet for XML Outputter -e --encoding encoding XML file encoding (UTF8, shift_jis, ISO-8859-1...) -b --brief-progress Use BriefTestProgressListener (default is TextTestProgressListener) -n --no-progress Show no test progress (disable default TextTestProgressListener) -t --text Use TextOutputter -o --cout Ouputters output to cout instead of the default cerr. filename[=3D"options"] Many filenames can be specified. They are the name of the test plug-ins to load. Optional plug-ins parameters can be specified after the filename by adding '=3D'. [:testpath] Optional. Only one test path can be specified. It must be prefixed with ':'. See TestPath constructor for syntax. 'parameters' (test plug-in or XML filename, test path...) may contains spaces if double quoted. Quote may be escaped with \". Some examples of command lines: DllPlugInTesterd_dll.exe -b -x tests.xml -c simple_plugind.dll CppUnitTestPlugInd.dll Will load 2 tests plug-ins (available in lib/), use the brief test progress, output the result in XML in file tests.xml and also output the result using the compiler outputter. DllPlugInTesterd_dll.exe ClockerPlugInd.dll=3D"flat" -n = CppUnitTestPlugInd.dll Will load the 2 test plug-ins, and pass the parameter string "flat" to the Clocker plug-in, disable test progress. Clocker being a test listener plug-ins (it doesn't implements any tests, it just register a TestListener), this is equivalent to say 'run all the test of CppUnitTestPlugIn and use ClockerPlugIn as a TestLisener'. DllPlugInTesterd_dll.exe CppUnitTestPlugInd.dll :Core Will run the test named "Core" (a suite in the present case ) of the test plug-in. * Documentation - New getting started documentation. Not completed yet, but probably a good complement to the current cookbook. Explore the creation of the Money example. * Examples - Money (examples/Money): the 'hello world' example. Unit tests for a simple Money class. - DllPlugInTesterTest (src/DllPlugInTester/DllPlugInTester.dsp): unit tests for CommandLineParser. Not really an example, but only slightly more complex than Money. - ClockerPlugIn (examples/ClockerPlugIn): a test listener plug-in that track tests and test suites running time. Parameter: "flat" for a reporting with a flattened tree. - DumperPlugIn (examples/DumperPlugIn): a test listener plug-in that dump the test tree as it run. Paramater: "flat" for a reporting with a flattened tree. - CppUnitTestPlugIn (examples/cppunitest/CppUnitTestPlugIn.dsp): CppUnit's test suite as a test plug-in. * Contribution - Contributed by project cuppa team (http://sourceforge.jp/projects/cuppa/): - Makefile for CppUnit with Borland C++ 5.5 free compiler: does not depend on a specific CppUnit version. * Compatiblity breaks - DllPlugInTester: (1.9.4 only), should add -c to DllPlugInTester command line. * Bug Fix: - DynamicLibaryManager did not report the library name when loading a a library. - BeosDynamicLibraryManager: fixed thanks to Shibu Yoshiki ('cuppa' project team). - Broken build on Unix should be fixed for most (thanks to Jeffrey Morgan). Enjoy, Baptiste. --- Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/ _______________________________________________ Cppunit-devel mailing list Cpp...@li... https://lists.sourceforge.net/lists/listinfo/cppunit-devel |
From: Steve M. R. <ste...@vi...> - 2002-04-22 22:59:35
|
On Mon, Apr 22, 2002 at 12:38:25PM -0500, Stanley Sutton wrote: > Also, the "-Wp,-MD,.deps/..." doesn't > seem to mean anything to the Solaris compiler, so the cp and the tr both fail. > If the purpose of the option is to generat dependancies, the -xM generates a > dependancy list to stdout, -xM1 generates a unique list with the /usr/include > files filtered out. Yes, that is the dependency-generating stuff from automake. I can't quickly find a list of compilers that automake supports, but it sounds like yours is not one of them. The automake team would probably like to know how to enable it for your compiler; send them email at <bug...@gn...>. In the meantime, automake supports a --disable-dependency-tracking that you can use. This may not be supported in automake versions prior to 1.5. On Mon, Apr 22, 2002 at 02:37:42PM -0500, Stanley Sutton wrote: > As near as I can figure, the problem is in the template instantation. I know > we've had problems with that in our code before, do to a compiler inker bug. > We use the linker option "-z now" on all of our Solaris compiles, as well as > absolute disk paths rather than relative ones to keep from confusing the > compiler/linker. However, I haven't been able to figure out how to add the "-z > now" to the linker. ".configure --prefix-/space/local_users/sutton/solaris > LD_FLAGS='-z now'" didn't seem to have any affect. The variable is "LDFLAGS". Setting it at configure time should work with autoconf 2.5x, I believe. If it doesn't, you can always set it on the "make" command line. -- by Rocket to the Moon, by Airplane to the Rocket, by Taxi to the Airport, by Frontdoor to the Taxi, by throwing back the blanket and laying down the legs ... - They Might Be Giants |
From: Baptiste L. <gai...@fr...> - 2002-04-23 08:19:16
|
Did you use ./autogen.sh too ? It does some stuff with aclocal. To fix that bug, remove the trailing ',' at the end of the enum. Baptiste. ----- Original Message ----- From: "Stanley Sutton" <su...@t-...> To: "Baptiste Lepilleur" <gai...@fr...>; <cpp...@li...> Sent: Monday, April 22, 2002 7:38 PM Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem Yes, I'm up to date on the tools, although since I don't have root access on my workstation, I use the --prefix on configure. Starting over from scratch fixed that particular problem. Once again, I'm getting: CC -DHAVE_CONFIG_H -I. -I. -I../../config -I../../include -I../../include -g -Wp,-MD,.deps/DynamicLibraryManager.pp -c DynamicLibraryManager.cpp -KPIC -DPIC CC: Warning: Option -Wp,-MD,.deps/DynamicLibraryManager.pp passed to ld, if ld is invoked, ignored otherwise "../../include/cppunit/plugin/DynamicLibraryManagerException.h", line 28: Error: Identifier expected instead of "}". 1 Error(s) detected. This is due to the enum in the include file, which ends in a ",}", which the Solaris compiler treats as an error. Also, the "-Wp,-MD,.deps/..." doesn't seem to mean anything to the Solaris compiler, so the cp and the tr both fail. If the purpose of the option is to generat dependancies, the -xM generates a dependancy list to stdout, -xM1 generates a unique list with the /usr/include files filtered out. -----Original Message----- From: Baptiste Lepilleur [mailto:gai...@fr...] Sent: Mon 22-Apr-02 11:24 To: Stanley Sutton; cpp...@li... Cc: Subject: Re: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem Did you follow the step indicated in Readme.CVS (and if those don't work, did you try the lastest tar ball ?): * Unix: To generate the configure script, you need several auxiliary tools. The version numbers are minimal: later versions should also work. autoconf 2.50 - see http://www.gnu.org/directory/autoconf.html automake 1.4 - see http://www.gnu.org/directory/automake.html libtool 1.4 - see http://www.gnu.org/directory/libtool.html After checking the sources out from CVS, you need to run the script sh autogen.sh from the top-level source directory (i.e. the one containing this file). This needs only to be done once. Baptiste. ----- Original Message ----- From: "Stanley Sutton" <su...@t-...> To: "Baptiste Lepilleur" <gai...@fr...>; <cpp...@li...> Sent: Monday, April 22, 2002 5:36 PM Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem I'm still having some problmes on Solaris 8, using the Forte 6 compiler. I removed all my local files and got a fresh CVS snapshot. Here's there first error: cd . && autoconf autoconf: warning: both `configure.ac' and `configure.in' are present. autoconf: warning: proceeding with `configure.ac'. configure.ac:37: error: do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ vs. LIBOBJS' I'm using GNU make, by the way, as well as the GNU versions of most of the utilities. -----Original Message----- From: Baptiste Lepilleur [mailto:gai...@fr...] Sent: Sun 21-Apr-02 08:28 To: cpp...@li... Cc: Subject: [Cppunit-devel] CppUnit 1.9.6 tar ball New snapshot. The problem on Unix should be fixed. Thanks to all those who helped ! KNOWN PROBLEMS: - TestPlugIn project has not been removed from the Examples workspace (just click cancel) - Money example is missing dependency with cppunit.dsp As usal, the snapshop can be found at: http://cppunit.sourceforge.net/snapshot/ http://cppunit.sourceforge.net/snapshot/cppunit-1.9.6.tar.gz http://cppunit.sourceforge.net/snapshot/cppunit-docs-1.9.6.tar.gz New in CppUnit 1.9.6: ---------------------- - DllPlugInTester can be parametrized from command line - Two test listener plug-in examples - An 'hello world' example & getting started document : Money - Contribution: generic makefile for Borland 5.5 free compiler. - Bug fixes * DllPlugInTester: - Advanced command line to support miscellaneous listener outputer. Parameters can now be passed to test plug-in: -c --compiler Use CompilerOutputter -x --xml [filename] Use XmlOutputter (if filename is omitted, then output to cout or cerr. -s --xsl stylesheet XML style sheet for XML Outputter -e --encoding encoding XML file encoding (UTF8, shift_jis, ISO-8859-1...) -b --brief-progress Use BriefTestProgressListener (default is TextTestProgressListener) -n --no-progress Show no test progress (disable default TextTestProgressListener) -t --text Use TextOutputter -o --cout Ouputters output to cout instead of the default cerr. filename[="options"] Many filenames can be specified. They are the name of the test plug-ins to load. Optional plug-ins parameters can be specified after the filename by adding '='. [:testpath] Optional. Only one test path can be specified. It must be prefixed with ':'. See TestPath constructor for syntax. 'parameters' (test plug-in or XML filename, test path...) may contains spaces if double quoted. Quote may be escaped with \". Some examples of command lines: DllPlugInTesterd_dll.exe -b -x tests.xml -c simple_plugind.dll CppUnitTestPlugInd.dll Will load 2 tests plug-ins (available in lib/), use the brief test progress, output the result in XML in file tests.xml and also output the result using the compiler outputter. DllPlugInTesterd_dll.exe ClockerPlugInd.dll="flat" -n CppUnitTestPlugInd.dll Will load the 2 test plug-ins, and pass the parameter string "flat" to the Clocker plug-in, disable test progress. Clocker being a test listener plug-ins (it doesn't implements any tests, it just register a TestListener), this is equivalent to say 'run all the test of CppUnitTestPlugIn and use ClockerPlugIn as a TestLisener'. DllPlugInTesterd_dll.exe CppUnitTestPlugInd.dll :Core Will run the test named "Core" (a suite in the present case ) of the test plug-in. * Documentation - New getting started documentation. Not completed yet, but probably a good complement to the current cookbook. Explore the creation of the Money example. * Examples - Money (examples/Money): the 'hello world' example. Unit tests for a simple Money class. - DllPlugInTesterTest (src/DllPlugInTester/DllPlugInTester.dsp): unit tests for CommandLineParser. Not really an example, but only slightly more complex than Money. - ClockerPlugIn (examples/ClockerPlugIn): a test listener plug-in that track tests and test suites running time. Parameter: "flat" for a reporting with a flattened tree. - DumperPlugIn (examples/DumperPlugIn): a test listener plug-in that dump the test tree as it run. Paramater: "flat" for a reporting with a flattened tree. - CppUnitTestPlugIn (examples/cppunitest/CppUnitTestPlugIn.dsp): CppUnit's test suite as a test plug-in. * Contribution - Contributed by project cuppa team (http://sourceforge.jp/projects/cuppa/): - Makefile for CppUnit with Borland C++ 5.5 free compiler: does not depend on a specific CppUnit version. * Compatiblity breaks - DllPlugInTester: (1.9.4 only), should add -c to DllPlugInTester command line. * Bug Fix: - DynamicLibaryManager did not report the library name when loading a a library. - BeosDynamicLibraryManager: fixed thanks to Shibu Yoshiki ('cuppa' project team). - Broken build on Unix should be fixed for most (thanks to Jeffrey Morgan). Enjoy, Baptiste. --- Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/ _______________________________________________ Cppunit-devel mailing list Cpp...@li... https://lists.sourceforge.net/lists/listinfo/cppunit-devel |
From: Baptiste L. <gai...@fr...> - 2002-04-23 08:19:18
|
I don't have a clue on how to do that (I know barely enough to update the automake/autoconf stuffs for each release). A tempory fix that might work would be to edit src/DllPlugInTester/makefile.am and add your flag to: DllPlugInTesterTest_LDFLAGS = -ldl What is that '-z now' option supposed to do ? This might bring some light about the source of the problem. Baptiste. ----- Original Message ----- From: "Stanley Sutton" <su...@t-...> To: "Baptiste Lepilleur" <gai...@fr...>; <cpp...@li...> Sent: Monday, April 22, 2002 9:37 PM Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem Here's the latest problem: gmake[2]: Entering directory `/space/local_users/sutton/projects/cppunit/src/DllPlugInTester' /bin/bash ../../libtool --mode=link CC -g -o DllPlugInTester -ldl DllPlugInTester.o CommandLineParser.o ../../src/cppunit/libcppunit.la CC -g -o .libs/DllPlugInTester DllPlugInTester.o CommandLineParser.o -ldl ../../src/cppunit/.libs/libcppunit.so -R/home/sutton/solaris/lib ild: (undefined symbol) unsigned std::deque<CppUnit::TestFailure*,std::allocator<CppUnit::TestFailure*> >::__buffer_size() -- referenced in ../../src/cppunit/.libs/libcppunit.so ild: (undefined symbol) std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*> >::iterator std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*> >::erase(std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*> >::iterator,std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*> >::iterator) -- referenced in ../../src/cppunit/.libs/libcppunit.so (plus many, many more in the same vein) As near as I can figure, the problem is in the template instantation. I know we've had problems with that in our code before, do to a compiler inker bug. We use the linker option "-z now" on all of our Solaris compiles, as well as absolute disk paths rather than relative ones to keep from confusing the compiler/linker. However, I haven't been able to figure out how to add the "-z now" to the linker. ".configure --prefix-/space/local_users/sutton/solaris LD_FLAGS='-z now'" didn't seem to have any affect. -----Original Message----- From: Baptiste Lepilleur [mailto:gai...@fr...] Sent: Mon 22-Apr-02 11:24 To: Stanley Sutton; cpp...@li... Cc: Subject: Re: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem Did you follow the step indicated in Readme.CVS (and if those don't work, did you try the lastest tar ball ?): * Unix: To generate the configure script, you need several auxiliary tools. The version numbers are minimal: later versions should also work. autoconf 2.50 - see http://www.gnu.org/directory/autoconf.html automake 1.4 - see http://www.gnu.org/directory/automake.html libtool 1.4 - see http://www.gnu.org/directory/libtool.html After checking the sources out from CVS, you need to run the script sh autogen.sh from the top-level source directory (i.e. the one containing this file). This needs only to be done once. Baptiste. ----- Original Message ----- From: "Stanley Sutton" <su...@t-...> To: "Baptiste Lepilleur" <gai...@fr...>; <cpp...@li...> Sent: Monday, April 22, 2002 5:36 PM Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem I'm still having some problmes on Solaris 8, using the Forte 6 compiler. I removed all my local files and got a fresh CVS snapshot. Here's there first error: cd . && autoconf autoconf: warning: both `configure.ac' and `configure.in' are present. autoconf: warning: proceeding with `configure.ac'. configure.ac:37: error: do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ vs. LIBOBJS' I'm using GNU make, by the way, as well as the GNU versions of most of the utilities. -----Original Message----- From: Baptiste Lepilleur [mailto:gai...@fr...] Sent: Sun 21-Apr-02 08:28 To: cpp...@li... Cc: Subject: [Cppunit-devel] CppUnit 1.9.6 tar ball New snapshot. The problem on Unix should be fixed. Thanks to all those who helped ! KNOWN PROBLEMS: - TestPlugIn project has not been removed from the Examples workspace (just click cancel) - Money example is missing dependency with cppunit.dsp As usal, the snapshop can be found at: http://cppunit.sourceforge.net/snapshot/ http://cppunit.sourceforge.net/snapshot/cppunit-1.9.6.tar.gz http://cppunit.sourceforge.net/snapshot/cppunit-docs-1.9.6.tar.gz New in CppUnit 1.9.6: ---------------------- - DllPlugInTester can be parametrized from command line - Two test listener plug-in examples - An 'hello world' example & getting started document : Money - Contribution: generic makefile for Borland 5.5 free compiler. - Bug fixes * DllPlugInTester: - Advanced command line to support miscellaneous listener outputer. Parameters can now be passed to test plug-in: -c --compiler Use CompilerOutputter -x --xml [filename] Use XmlOutputter (if filename is omitted, then output to cout or cerr. -s --xsl stylesheet XML style sheet for XML Outputter -e --encoding encoding XML file encoding (UTF8, shift_jis, ISO-8859-1...) -b --brief-progress Use BriefTestProgressListener (default is TextTestProgressListener) -n --no-progress Show no test progress (disable default TextTestProgressListener) -t --text Use TextOutputter -o --cout Ouputters output to cout instead of the default cerr. filename[="options"] Many filenames can be specified. They are the name of the test plug-ins to load. Optional plug-ins parameters can be specified after the filename by adding '='. [:testpath] Optional. Only one test path can be specified. It must be prefixed with ':'. See TestPath constructor for syntax. 'parameters' (test plug-in or XML filename, test path...) may contains spaces if double quoted. Quote may be escaped with \". Some examples of command lines: DllPlugInTesterd_dll.exe -b -x tests.xml -c simple_plugind.dll CppUnitTestPlugInd.dll Will load 2 tests plug-ins (available in lib/), use the brief test progress, output the result in XML in file tests.xml and also output the result using the compiler outputter. DllPlugInTesterd_dll.exe ClockerPlugInd.dll="flat" -n CppUnitTestPlugInd.dll Will load the 2 test plug-ins, and pass the parameter string "flat" to the Clocker plug-in, disable test progress. Clocker being a test listener plug-ins (it doesn't implements any tests, it just register a TestListener), this is equivalent to say 'run all the test of CppUnitTestPlugIn and use ClockerPlugIn as a TestLisener'. DllPlugInTesterd_dll.exe CppUnitTestPlugInd.dll :Core Will run the test named "Core" (a suite in the present case ) of the test plug-in. * Documentation - New getting started documentation. Not completed yet, but probably a good complement to the current cookbook. Explore the creation of the Money example. * Examples - Money (examples/Money): the 'hello world' example. Unit tests for a simple Money class. - DllPlugInTesterTest (src/DllPlugInTester/DllPlugInTester.dsp): unit tests for CommandLineParser. Not really an example, but only slightly more complex than Money. - ClockerPlugIn (examples/ClockerPlugIn): a test listener plug-in that track tests and test suites running time. Parameter: "flat" for a reporting with a flattened tree. - DumperPlugIn (examples/DumperPlugIn): a test listener plug-in that dump the test tree as it run. Paramater: "flat" for a reporting with a flattened tree. - CppUnitTestPlugIn (examples/cppunitest/CppUnitTestPlugIn.dsp): CppUnit's test suite as a test plug-in. * Contribution - Contributed by project cuppa team (http://sourceforge.jp/projects/cuppa/): - Makefile for CppUnit with Borland C++ 5.5 free compiler: does not depend on a specific CppUnit version. * Compatiblity breaks - DllPlugInTester: (1.9.4 only), should add -c to DllPlugInTester command line. * Bug Fix: - DynamicLibaryManager did not report the library name when loading a a library. - BeosDynamicLibraryManager: fixed thanks to Shibu Yoshiki ('cuppa' project team). - Broken build on Unix should be fixed for most (thanks to Jeffrey Morgan). Enjoy, Baptiste. --- Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/ _______________________________________________ Cppunit-devel mailing list Cpp...@li... https://lists.sourceforge.net/lists/listinfo/cppunit-devel |
From: Stanley S. <su...@t-...> - 2002-04-23 14:06:11
|
It forces the linker to us ld instead of ild, and forces using = templates in the library defined, rather than deferring to last possible = moment. I think it's similar to creating a "closed library" on HP. I = know on our software at work, we have to use it to make our libraries = function correctly (we create about 10 shared libraries on the way to = creating our executable, and it never worked correctly until we added = the option. We've reported the problem to Sun, but haven't gotten any = feedback on it). -----Original Message----- From: Baptiste Lepilleur [mailto:gai...@fr...] Sent: Mon 22-Apr-02 16:17 To: Stanley Sutton; cpp...@li... Cc:=09 Subject: Re: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem I don't have a clue on how to do that (I know barely enough to update = the automake/autoconf stuffs for each release). A tempory fix that might work would be to edit src/DllPlugInTester/makefile.am and add your flag to: DllPlugInTesterTest_LDFLAGS =3D -ldl What is that '-z now' option supposed to do ? This might bring some = light about the source of the problem. Baptiste. ----- Original Message ----- From: "Stanley Sutton" <su...@t-...> To: "Baptiste Lepilleur" <gai...@fr...>; <cpp...@li...> Sent: Monday, April 22, 2002 9:37 PM Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem Here's the latest problem: gmake[2]: Entering directory `/space/local_users/sutton/projects/cppunit/src/DllPlugInTester' /bin/bash ../../libtool --mode=3Dlink CC -g -o DllPlugInTester -ldl DllPlugInTester.o CommandLineParser.o ../../src/cppunit/libcppunit.la CC -g -o .libs/DllPlugInTester DllPlugInTester.o CommandLineParser.o = -ldl ../../src/cppunit/.libs/libcppunit.so -R/home/sutton/solaris/lib ild: (undefined symbol) unsigned std::deque<CppUnit::TestFailure*,std::allocator<CppUnit::TestFailure*> >::__buffer_size() -- referenced in = ../../src/cppunit/.libs/libcppunit.so ild: (undefined symbol) std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*> >::iterator std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*> >::erase(std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*> >::iterator,std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*> >::iterator) -- referenced in ../../src/cppunit/.libs/libcppunit.so (plus many, many more in the same vein) As near as I can figure, the problem is in the template instantation. I know we've had problems with that in our code before, do to a compiler = inker bug. We use the linker option "-z now" on all of our Solaris compiles, = as well as absolute disk paths rather than relative ones to keep from = confusing the compiler/linker. However, I haven't been able to figure out how to = add the "-z now" to the linker. ".configure --prefix-/space/local_users/sutton/solaris LD_FLAGS=3D'-z = now'" didn't seem to have any affect. -----Original Message----- From: Baptiste Lepilleur [mailto:gai...@fr...] Sent: Mon 22-Apr-02 11:24 To: Stanley Sutton; cpp...@li... Cc: Subject: Re: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem Did you follow the step indicated in Readme.CVS (and if those don't = work, did you try the lastest tar ball ?): * Unix: To generate the configure script, you need several auxiliary tools. The version numbers are minimal: later versions should also work. autoconf 2.50 - see http://www.gnu.org/directory/autoconf.html automake 1.4 - see http://www.gnu.org/directory/automake.html libtool 1.4 - see http://www.gnu.org/directory/libtool.html After checking the sources out from CVS, you need to run the script sh autogen.sh from the top-level source directory (i.e. the one containing this file). This needs only to be done once. Baptiste. ----- Original Message ----- From: "Stanley Sutton" <su...@t-...> To: "Baptiste Lepilleur" <gai...@fr...>; <cpp...@li...> Sent: Monday, April 22, 2002 5:36 PM Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem I'm still having some problmes on Solaris 8, using the Forte 6 compiler. = I removed all my local files and got a fresh CVS snapshot. Here's there = first error: cd . && autoconf autoconf: warning: both `configure.ac' and `configure.in' are present. autoconf: warning: proceeding with `configure.ac'. configure.ac:37: error: do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ vs. LIBOBJS' I'm using GNU make, by the way, as well as the GNU versions of most of = the utilities. -----Original Message----- From: Baptiste Lepilleur [mailto:gai...@fr...] Sent: Sun 21-Apr-02 08:28 To: cpp...@li... Cc: Subject: [Cppunit-devel] CppUnit 1.9.6 tar ball New snapshot. The problem on Unix should be fixed. Thanks to all = those who helped ! KNOWN PROBLEMS: - TestPlugIn project has not been removed from the Examples workspace = (just click cancel) - Money example is missing dependency with cppunit.dsp As usal, the snapshop can be found at: http://cppunit.sourceforge.net/snapshot/ http://cppunit.sourceforge.net/snapshot/cppunit-1.9.6.tar.gz http://cppunit.sourceforge.net/snapshot/cppunit-docs-1.9.6.tar.gz New in CppUnit 1.9.6: ---------------------- - DllPlugInTester can be parametrized from command line - Two test listener plug-in examples - An 'hello world' example & getting started document : Money - Contribution: generic makefile for Borland 5.5 free compiler. - Bug fixes * DllPlugInTester: - Advanced command line to support miscellaneous listener outputer. Parameters can now be passed to test plug-in: -c --compiler Use CompilerOutputter -x --xml [filename] Use XmlOutputter (if filename is omitted, then output to cout or cerr. -s --xsl stylesheet XML style sheet for XML Outputter -e --encoding encoding XML file encoding (UTF8, shift_jis, ISO-8859-1...) -b --brief-progress Use BriefTestProgressListener (default is TextTestProgressListener) -n --no-progress Show no test progress (disable default TextTestProgressListener) -t --text Use TextOutputter -o --cout Ouputters output to cout instead of the default cerr. filename[=3D"options"] Many filenames can be specified. They are the name of the test plug-ins to load. Optional plug-ins parameters can be specified after the filename by adding '=3D'. [:testpath] Optional. Only one test path can be specified. It must be prefixed with ':'. See TestPath constructor for syntax. 'parameters' (test plug-in or XML filename, test path...) may contains spaces if double quoted. Quote may be escaped with \". Some examples of command lines: DllPlugInTesterd_dll.exe -b -x tests.xml -c simple_plugind.dll CppUnitTestPlugInd.dll Will load 2 tests plug-ins (available in lib/), use the brief test progress, output the result in XML in file tests.xml and also output the result using the compiler outputter. DllPlugInTesterd_dll.exe ClockerPlugInd.dll=3D"flat" -n = CppUnitTestPlugInd.dll Will load the 2 test plug-ins, and pass the parameter string "flat" to the Clocker plug-in, disable test progress. Clocker being a test listener plug-ins (it doesn't implements any tests, it just register a TestListener), this is equivalent to say 'run all the test of CppUnitTestPlugIn and use ClockerPlugIn as a TestLisener'. DllPlugInTesterd_dll.exe CppUnitTestPlugInd.dll :Core Will run the test named "Core" (a suite in the present case ) of the test plug-in. * Documentation - New getting started documentation. Not completed yet, but probably a good complement to the current cookbook. Explore the creation of the Money example. * Examples - Money (examples/Money): the 'hello world' example. Unit tests for a simple Money class. - DllPlugInTesterTest (src/DllPlugInTester/DllPlugInTester.dsp): unit tests for CommandLineParser. Not really an example, but only slightly more complex than Money. - ClockerPlugIn (examples/ClockerPlugIn): a test listener plug-in that track tests and test suites running time. Parameter: "flat" for a reporting with a flattened tree. - DumperPlugIn (examples/DumperPlugIn): a test listener plug-in that dump the test tree as it run. Paramater: "flat" for a reporting with a flattened tree. - CppUnitTestPlugIn (examples/cppunitest/CppUnitTestPlugIn.dsp): CppUnit's test suite as a test plug-in. * Contribution - Contributed by project cuppa team (http://sourceforge.jp/projects/cuppa/): - Makefile for CppUnit with Borland C++ 5.5 free compiler: does not depend on a specific CppUnit version. * Compatiblity breaks - DllPlugInTester: (1.9.4 only), should add -c to DllPlugInTester command line. * Bug Fix: - DynamicLibaryManager did not report the library name when loading a a library. - BeosDynamicLibraryManager: fixed thanks to Shibu Yoshiki ('cuppa' project team). - Broken build on Unix should be fixed for most (thanks to Jeffrey Morgan). Enjoy, Baptiste. --- Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/ _______________________________________________ Cppunit-devel mailing list Cpp...@li... https://lists.sourceforge.net/lists/listinfo/cppunit-devel |
From: Stanley S. <su...@t-...> - 2002-04-23 14:12:07
|
I'll give that a try, if I can figure out where to supply arguments to = automake. I'm not that familar with the GNU auto* tools, we use a = combination of perl and shell scripts to maintain our multi-platform = build system. It has the advantage of being much faster, but the = disadvantage of being tailored to supporting our own system, not anyone = else's. -----Original Message----- From: Steve M. Robbins [mailto:ste...@vi...] Sent: Mon 22-Apr-02 17:59 To: Stanley Sutton Cc: CppUnit Development Subject: Re: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem On Mon, Apr 22, 2002 at 12:38:25PM -0500, Stanley Sutton wrote: > Also, the "-Wp,-MD,.deps/..." doesn't > seem to mean anything to the Solaris compiler, so the cp and the tr = both fail.=20 > If the purpose of the option is to generat dependancies, the -xM = generates a > dependancy list to stdout, -xM1 generates a unique list with the = /usr/include > files filtered out. Yes, that is the dependency-generating stuff from automake. I can't quickly find a list of compilers that automake supports, but it sounds like yours is not one of them. The automake team would probably like to know how to enable it for your compiler; send them email at <bug...@gn...>. In the meantime, automake supports a --disable-dependency-tracking that you can use. This may not be supported in automake versions prior to 1.5. On Mon, Apr 22, 2002 at 02:37:42PM -0500, Stanley Sutton wrote: > As near as I can figure, the problem is in the template instantation. = I know > we've had problems with that in our code before, do to a compiler = inker bug.=20 > We use the linker option "-z now" on all of our Solaris compiles, as = well as > absolute disk paths rather than relative ones to keep from confusing = the > compiler/linker. However, I haven't been able to figure out how to = add the "-z > now" to the linker. ".configure = --prefix-/space/local_users/sutton/solaris > LD_FLAGS=3D'-z now'" didn't seem to have any affect. The variable is "LDFLAGS". =20 Setting it at configure time should work with autoconf 2.5x, I believe. If it doesn't, you can always set it on the "make" command line. --=20 by Rocket to the Moon, by Airplane to the Rocket, by Taxi to the Airport, by Frontdoor to the Taxi, by throwing back the blanket and laying down the legs ... - They Might Be Giants _______________________________________________ Cppunit-devel mailing list Cpp...@li... https://lists.sourceforge.net/lists/listinfo/cppunit-devel |
From: Steve M. R. <ste...@vi...> - 2002-04-22 16:06:25
|
On Mon, Apr 22, 2002 at 10:36:59AM -0500, Stanley Sutton wrote: > > I'm still having some problmes on Solaris 8, using the Forte 6 compiler. I > removed all my local files and got a fresh CVS snapshot. Here's there first > error: > > cd . && autoconf > autoconf: warning: both `configure.ac' and `configure.in' are present. > autoconf: warning: proceeding with `configure.ac'. ??? How did that happen? I just ran "cvs update" and there is only configure.in here. > configure.ac:37: error: do not use LIBOBJS directly, use AC_LIBOBJ > (see section `AC_LIBOBJ vs. LIBOBJS' Neither is there any "LIBOBJ" in my configure.in. Something is fishy. -S -- by Rocket to the Moon, by Airplane to the Rocket, by Taxi to the Airport, by Frontdoor to the Taxi, by throwing back the blanket and laying down the legs ... - They Might Be Giants |
From: Baptiste L. <gai...@fr...> - 2002-04-22 17:17:54
|
Did you follow the step indicated in Readme.CVS (and if those don't work, did you try the lastest tar ball ?): * Unix: To generate the configure script, you need several auxiliary tools. The version numbers are minimal: later versions should also work. autoconf 2.50 - see http://www.gnu.org/directory/autoconf.html automake 1.4 - see http://www.gnu.org/directory/automake.html libtool 1.4 - see http://www.gnu.org/directory/libtool.html After checking the sources out from CVS, you need to run the script sh autogen.sh from the top-level source directory (i.e. the one containing this file). This needs only to be done once. Baptiste. ----- Original Message ----- From: "Stanley Sutton" <su...@t-...> To: "Baptiste Lepilleur" <gai...@fr...>; <cpp...@li...> Sent: Monday, April 22, 2002 5:36 PM Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem I'm still having some problmes on Solaris 8, using the Forte 6 compiler. I removed all my local files and got a fresh CVS snapshot. Here's there first error: cd . && autoconf autoconf: warning: both `configure.ac' and `configure.in' are present. autoconf: warning: proceeding with `configure.ac'. configure.ac:37: error: do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ vs. LIBOBJS' I'm using GNU make, by the way, as well as the GNU versions of most of the utilities. -----Original Message----- From: Baptiste Lepilleur [mailto:gai...@fr...] Sent: Sun 21-Apr-02 08:28 To: cpp...@li... Cc: Subject: [Cppunit-devel] CppUnit 1.9.6 tar ball New snapshot. The problem on Unix should be fixed. Thanks to all those who helped ! KNOWN PROBLEMS: - TestPlugIn project has not been removed from the Examples workspace (just click cancel) - Money example is missing dependency with cppunit.dsp As usal, the snapshop can be found at: http://cppunit.sourceforge.net/snapshot/ http://cppunit.sourceforge.net/snapshot/cppunit-1.9.6.tar.gz http://cppunit.sourceforge.net/snapshot/cppunit-docs-1.9.6.tar.gz New in CppUnit 1.9.6: ---------------------- - DllPlugInTester can be parametrized from command line - Two test listener plug-in examples - An 'hello world' example & getting started document : Money - Contribution: generic makefile for Borland 5.5 free compiler. - Bug fixes * DllPlugInTester: - Advanced command line to support miscellaneous listener outputer. Parameters can now be passed to test plug-in: -c --compiler Use CompilerOutputter -x --xml [filename] Use XmlOutputter (if filename is omitted, then output to cout or cerr. -s --xsl stylesheet XML style sheet for XML Outputter -e --encoding encoding XML file encoding (UTF8, shift_jis, ISO-8859-1...) -b --brief-progress Use BriefTestProgressListener (default is TextTestProgressListener) -n --no-progress Show no test progress (disable default TextTestProgressListener) -t --text Use TextOutputter -o --cout Ouputters output to cout instead of the default cerr. filename[="options"] Many filenames can be specified. They are the name of the test plug-ins to load. Optional plug-ins parameters can be specified after the filename by adding '='. [:testpath] Optional. Only one test path can be specified. It must be prefixed with ':'. See TestPath constructor for syntax. 'parameters' (test plug-in or XML filename, test path...) may contains spaces if double quoted. Quote may be escaped with \". Some examples of command lines: DllPlugInTesterd_dll.exe -b -x tests.xml -c simple_plugind.dll CppUnitTestPlugInd.dll Will load 2 tests plug-ins (available in lib/), use the brief test progress, output the result in XML in file tests.xml and also output the result using the compiler outputter. DllPlugInTesterd_dll.exe ClockerPlugInd.dll="flat" -n CppUnitTestPlugInd.dll Will load the 2 test plug-ins, and pass the parameter string "flat" to the Clocker plug-in, disable test progress. Clocker being a test listener plug-ins (it doesn't implements any tests, it just register a TestListener), this is equivalent to say 'run all the test of CppUnitTestPlugIn and use ClockerPlugIn as a TestLisener'. DllPlugInTesterd_dll.exe CppUnitTestPlugInd.dll :Core Will run the test named "Core" (a suite in the present case ) of the test plug-in. * Documentation - New getting started documentation. Not completed yet, but probably a good complement to the current cookbook. Explore the creation of the Money example. * Examples - Money (examples/Money): the 'hello world' example. Unit tests for a simple Money class. - DllPlugInTesterTest (src/DllPlugInTester/DllPlugInTester.dsp): unit tests for CommandLineParser. Not really an example, but only slightly more complex than Money. - ClockerPlugIn (examples/ClockerPlugIn): a test listener plug-in that track tests and test suites running time. Parameter: "flat" for a reporting with a flattened tree. - DumperPlugIn (examples/DumperPlugIn): a test listener plug-in that dump the test tree as it run. Paramater: "flat" for a reporting with a flattened tree. - CppUnitTestPlugIn (examples/cppunitest/CppUnitTestPlugIn.dsp): CppUnit's test suite as a test plug-in. * Contribution - Contributed by project cuppa team (http://sourceforge.jp/projects/cuppa/): - Makefile for CppUnit with Borland C++ 5.5 free compiler: does not depend on a specific CppUnit version. * Compatiblity breaks - DllPlugInTester: (1.9.4 only), should add -c to DllPlugInTester command line. * Bug Fix: - DynamicLibaryManager did not report the library name when loading a a library. - BeosDynamicLibraryManager: fixed thanks to Shibu Yoshiki ('cuppa' project team). - Broken build on Unix should be fixed for most (thanks to Jeffrey Morgan). Enjoy, Baptiste. --- Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/ _______________________________________________ Cppunit-devel mailing list Cpp...@li... https://lists.sourceforge.net/lists/listinfo/cppunit-devel |