On 30.03.2013 21:43, Jeff Trawick wrote:
> Tarballs/zipfiles are at http://apr.apache.org/dev/dist/
> 
> Shortcuts to CHANGES:
> 
> http://apr.apache.org/dev/dist/CHANGES-APR-UTIL-1.5.2
> http://apr.apache.org/dev/dist/CHANGES-APR-UTIL-1.5
> 
> autoconf version: 2.69 (same as 1.5.1)
> libtool version: 2.4.2 (1.5.1 had "2.4.2 Debian-2.4.2-1.1"
> 
> +/-1
> [+1] Release APR-util 1.5.2 as GA
> 

My test results:

No regressions.

Summary
=======

- some libtool m4 files not deleted by buildconf (see below)

- crypto configure for OpenSSL at least fails on Solaris,
   because when linking against the libssl we need
   the additional flags "-ldl -lsocket -lnsl". Currently
   there's no way to fix this apart from hacking configure.
   For Linux I'm not sure, but likely you'll need "-ldl".

- LDADD flags are typically not respected during configure,
  only during the make.

- configure fails for Berkeley DB in non-standard path,
   because it doesn't add an rpath to conftest and then tries
   to run the compiled conftest binary.

- no rpath for ldap, mysql and crypto dso extensions. So no
   way to run the result without LD_LIBRARY_PATH.
   Interesting: the m4 file does add an rpath only for oracle.
   Since there's no platform independent way to add rpath,
   we might want to remove it everywhere (and users would need
   to use the respective LDADD variables).

- no rpath for dependency libs when building without dso support,
   e.g. when the ldap, crypto, mysql, oracle, sqlite etc. extensions
   are all in the big apr util library.

- testall sometimes fails in testpass on Linux and often fails
  in testcrypto when testing nss passphrase (see below).

- Windows Build system:
   - test/testutildll.dsp is the only DSP containing "Release9x" and
     "Debug9x" configuration info. IMHO that's obsolete and could
     be removed. Probably also in Makefile.win?

Details
=======

- svn compared with gz, bz2 and zip only expected differences
   except for the following in the directory xml/expat/conftools
   which are not a blocker;
   IMHO we could remove those at the and of buildconf
     libtool.m4
     lt~obsolete.m4
     ltoptions.m4
     ltsugar.m4
     ltversion.m4

- files signed, checksums correct

- built and made check on the following platforms:

   - Solaris 8 and 10 Sparc (gcc 4.1.2 resp. 4.7.2)
   - SuSE Linux Enterprise 10 32 Bit and 10 and 11 64 Bit
   - RedHat Enterprise Linux 5 and 6 64 Bit

   - using all combinations of:

     - apr 1.4.6 / 1.4.x r1462907
     - expat builtin / 2.1.0
     - OpenSSL 1.0.1e (plus a few patches)
     - dso disable / enable
     - Berkeley DB 5.3.21
     - sqlite 3.7.15.2
     - mysql 6.0.2 (only Solaris)
     - oracle 11.2.0.2.0 (Solaris 10), resp. 10.2.0.5.0 (Solaris 8)
     - platform nss (Solaris 10 and RHEL 5 and 6)

- make check for the successful build ran fine for 110 build,
  but failed for 58 builds:

   - two failures in testdbm on SLES 11 without DSO,
     *not* reproducible (Failed 1 of 2)
     Though not reproducible exactly the same failure happened
     when testing 1.5.0 and 1.5.1. Maybe due to increased
     load during the parallel builds and checks on the
     virtualized server. Could be a race condition.

   - 16 failures only on RHEL 5 when DSO is disabled due to
     segmentation fault in testcrypto. Searching for the stack
     indicates, that the nss library might have been used after
     some sort of shutdown. For details see my 1.5.1 vote mail.

   - 40 failures in testcrypto
     testing crypto for nss gives errors on Solaris 10 and on RHEL
     where I had built crypto with nss and OpenSSL (no nss build
     on the other platforms). For details see my 1.5.1 vote mail.

- I have not run the httpd test framework against those builds

Regards,

Rainer

Reply via email to