Kevin Radke writes:
> So far the build without the --disable-nonportable-atomics flag seems to
> working much better with httpd 2.2.29, svn 1.8.13, and apr 1.5.1. I'm no
> longer seeing the assert when using the worker mpm on a heavily loaded
> multi-core system.
Interesting, I wonder if there
Philip,
So far the build without the --disable-nonportable-atomics flag seems to
working much better with httpd 2.2.29, svn 1.8.13, and apr 1.5.1. I'm no
longer seeing the assert when using the worker mpm on a heavily loaded
multi-core system.
Thanks!
Kevin R.
On Wed, Apr 15, 2015 at 11:26 AM,
Philip,
I believe the non-portable-atomics flag is left over from getting 1.7
working due to the original APR bug. Since the bug is fixed, I'll try
without the flag and see what happens.
A make check for this apr also succeeds without any issues.
APR Lock Performance Test
==
apr_th
Kevin Radke writes:
> I'm using --disable-nonportable-atomics and apr 1.5.1 compiled with gcc
> 4.4.7.
> httpd 2.2.29 is built with mpm=worker.
Do you have a particular reason for using --disable-nonportable-atomics?
I suspect it leads to code that is not used as often and thus less well
tested.
Philip,
I'm using --disable-nonportable-atomics and apr 1.5.1 compiled with gcc
4.4.7.
httpd 2.2.29 is built with mpm=worker.
make check in svn gives:
Summary of test results:
1948 tests PASSED
58 tests SKIPPED
31 tests XFAILED (1 WORK-IN-PROGRESS)
SUMMARY: All tests successful.
Kevin R,
Kevin Radke writes:
> I recently built svn 1.8.13 on a x64 Linux machine with self-built
> dependencies that are current for Apache 2.2.29 (mpm=worker). I'm seeing
> the following exception periodically and I'm looking for help to try and
> figure out the cause.
>
>
> httpd: subversion/libsvn_su
