axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Darroch (JIRA)" <>
Subject [jira] Commented: (AXIS2C-376) --enable-tests and "make check" has multiple errors
Date Thu, 26 Oct 2006 00:26:17 GMT
    [ ] 
Chris Darroch commented on AXIS2C-376:

Just as a note, that last set of patches to the files isn't really
suitable for use against the svn trunk -- you'd want to turn them into
patches against the files.  But hopefully you'll get the idea
of what I'm doing.

> --enable-tests and "make check" has multiple errors
> ---------------------------------------------------
>                 Key: AXIS2C-376
>                 URL:
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: build system (Unix/Linux)
>    Affects Versions: 0.94
>         Environment: Unix/Linux, maybe others
>            Reporter: Chris Darroch
>            Priority: Minor
>         Attachments: axis2c-376.patch, axis2c-376.patch
> Normally, when using a package built with autoconf, one can expect to do:
> ./configure --enable-tests
> make check
> For Axis2/C this runs into a variety of problems.  I noted a few of these issues
> in AXIS2C-313 as well, but this is a more detailed summary of the problems I've seen.
> Specifically:
> 1) The libcutest library is required, but it's a non-standard library, and isn't even
installed as part
> of the CuTest package -- it has to be built by hand.
> 2) A number of the test programs have errors; for example, they free their env variable
early and then segfault, or report a failure when none has occurred.
> 3) Test resource files are referenced that aren't supplied in the package, for example,
> 4) Some of the tests require that AXIS2C_HOME be set and that a valid axis2.xml file
> 5) If --enable-tests is used for ./configure, then when "make install" runs in the test
> it installs various programs and libraries in directories named itest, unit_test, and
> under the specified --prefix.  Even if these programs should be installed (which is arguable),
> they should be installed under the --bindir and --libdir locations, not --prefix.
> In my case, we try to make running "make check" a standard part of our global package
> installation framework, which is automated.  I'll attach as files (if I can) the various
> we make to the Axis2/C test framework to deal with problems #2, #3, #4 and #5.
> To deal with problem #3 we also unpack the following resources, which I hunted around
> for on
>   into xml_schema
>   into woden/test
> To deal with problem #4, we patch samples/server/axis2.xml to not engage
> the addressing module, and then point AXIS2C_HOME to samples/server
> in our build directory before running "make check".  That allows the tests to run
> without having already done a "make install" -- since our installation framework won't
> install the package until it's seen a successful "make check" run!
> Finally, to deal with problem #1, we build and install libcutest prior to building, testing,
> and installing Axis2/C, using the CuTest package and the trick found in this
> axis-c-dev mailing list posting:
> In general, though, all these tricks shouldn't be necessary.  A user should be able to
> download the axis2c package, run ./configure --enable-tests and "make check" with
> no special knowledge, I believe.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message