Travis Cross a973fb6347 Fix memset calls in APR sha2 implementation
The implementation clears the context / state data from memory when it
is finished with it.  Prior to this commit, however, it was actually
only clearing the first 4 bytes on x86 or 8 bytes on x86_64.

clang warns:

  warning: argument to 'sizeof' in 'memset' call is the same
  expression as the destination; did you mean to dereference it?
      [-Wsizeof-pointer-memaccess]
2012-06-24 08:05:25 +00:00
..
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2007-11-08 13:45:57 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2010-09-27 13:26:09 -05:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2010-09-27 13:26:09 -05:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2009-02-16 07:11:19 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00
2006-12-19 19:58:23 +00:00

Apache Portable Runtime
=======================

If you are building APR from SVN, you need to use a slightly non-standard
build process.  You must have autoconf and libtool installed for this to
work.  There are three steps:

1) ./buildconf
2) ./configure
3) make

If you are building APR from a distribution tarball, buildconf will have
already been run for you, and you therefore do not need to have either
autoconf or libtool installed, and you do not need to run buildconf.  Skip
step one above and just run configure then make.

Generating Test Coverage information
====================================

If you want to generate test coverage data, use the following steps:

1) ./buildconf
2) CFLAGS="-fprofile-arcs -ftest-coverage" ./configure
3) make
4) cd test
5) make
6) ./testall
7) cd ..
8) make gcov