Jean-Sebastien Delfino wrote:
[...]
I downloaded your 4.1.3 release, compiled it on Redhat Enterprise Linux
4, and ran some of your samples.
I have two questions:
- How do I run all your test cases?
Unfortunately, in 4.1.3 you need to run them one at a time by hand
(the stdcxx test suite was and still is being migrated from the
Rogue Wave test harness and so things have been a bit in flux).
Alternatively, you can try applying the following patch to see
if it resolves the problem:
http://svn.apache.org/viewvc?view=rev&revision=419995
This is resolved on trunk (where make run works again).
I found a run executable in
build/test, tried ./run ./* and got this:
Invoking the run script directly will work but using make run is
the recommended way to run the tests and examples (and locales).
Summary: out of 69 programs
45 exited with non-zero status
The tests fail due to incompatible command line options being passed
to them by the test harness. This is the subject of the already fixed
STDCXX-254: http://issues.apache.org/jira/browse/STDCXX-254.
24 failed to compile
I'm not sure what exactly is behind these failures but it's not
anything in the library.
0 failed to link
0 failed at least one assertion
0 exited with a signal
0 killed with signal 9
no regressions (this is baseline)
34% pass rate
I'm assuming that the failures are my problem and I'm not running this
correctly since all the samples I tried worked nicely :)
They're not your problem but they're nothing to worry about, either.
FWIW, we're working on publishing stdcxx test results across all our
platforms. This project is very much in a proof of concept stage but
you can get a glimpse of what it might look like here (ignore the
links on the page, they are not functional yet):
http://people.apache.org/~sebor/stdcxx-results.html
- Also, I noticed that the build generates .a files. Is there an option
to generate a .so shared library?
Yes, there certainly is. For now you can use the BUILDMODE make
variable. In the (near) future we also plan to provide a configure
like interface to the build infrastructure to let people use the
usual --enable-xxx switches (such as --enable-shared).
The BUILDMODE variable is specified as taking a <build-mode>
argument defined in the README as follows:
<build-mode> is a comma-separated list of keywords describing how
to build the library and the rest of the
binaries. The following arguments are recognized:
dcethreads - create a thread-safe library, use DCE
threads
debug - include debugging information
optimized - optimized
pthreads - create a thread safe library, use POSIX
threads
shared - create a shared library (archive is default)
shared,archive - create an AIX shared archive
threads - create a thread-safe library, use Solaris
threads
wide - generate wide (64-bit) code
Read the full details here:
http://svn.apache.org/repos/asf/incubator/stdcxx/trunk/etc/config/README
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
